For security reasons I am switching to a different account on my development machine. After adding this new account to Windows and setting up the Visual Studio configuration for this new account, I thought I was good to go.
So I opened a first solution inside my fresh Visual Studio instance. Everything looked OK at first sight, but then I noticed a small warning message at the right bottom corner of my Visual Studio:
And when I took a look at the Git Changes window, no changes were shown:
What is going on?
Starting from Git v2.35.2, Git now checks for ownership of the folder trying to ensure that the folder you are using Git in has the same user as the owner as your current user account. As the original Git repo(and corresponding Windows folders) was created using a different account, Git considers this repository as unsafe.
This check was introduced in Git to tackle a security issue which allows parent repositories directories to override permissions of child repositories in some situations which would potentially allow execution of commands with unintended consequences.
Git Security Issue: CVE-2022-24765
How to fix this?
The good news is that you can fix this directly inside Visual Studio. Let me show you how:
-
Click on the untrusted repo in the bottom right corner of Visual Studio:
-
The list of known repositories is shown. You’ll find the untrusted repository under Other. Right click on this repository:
-
If you choose Trust repository from the context menu, the repository is added to the list of trusted repositories and you can start using Git again.
-
You also have the option to click on View Trust Details. This will open a pop up with more details. Here you can click on Trust and continue to mark the repository as trusted.
