fatal: unsafe repository ('' is owned by someone else)

[bobbytreed]

Does this issue occur when all extensions are disabled?: Yes/No

• VS Code Version: 1.67
• OS Version: Win 21H2

Steps to Reproduce:

1. Use the openRepository command to open a repo that is not added to 'safe.directory'
2. reference: 6b241a6
3. There is a caught exception that states the following

'fatal: unsafe repository ('' is owned by someone else)
To add an exception for this directory, call:

	git config --global --add safe.directory 

Obviously, for security purposes, an extension wouldn't want to just add this value for the user, so it would be nice to provide the same dialog that vsCode uses (though for a different purpose), that asks the user if they want to trust the repository.

You could certainly say that this is not a vsCode issue and that such a dialog shouldn't be handled internally by vscode, and I wouldn't be able to argue. In the meantime, I would probably look into prompting the user for trust and then use 'child_process' to exec git config global' Could you at least point me to where I can pick up the error without just debugging all "CaughtExceptions"?

[snickler]

I actually received this same issue outside of VSCode, running a simple 'git status' on my local Git repository.

I'm running Git version 2.36.0.windows.1.

[redbaron]

Proper fix is to change repository owner to the current user

[sprintska]

I actually received this same issue outside of VSCode, running a simple 'git status' on my local Git repository.

I'm running Git version 2.36.0.windows.1.

Same issue here. A little more research turned up that it's related to a recent git update from 2.35.2 to address CVE-2022-24765.

In my case, I'm working from a network drive, so "just fix the owner" isn't a workable solution.

For posterity, since this was the top hit on Google for it for me, there's some discussion on it here on StackOverflow.

Personally, since I can accept the risk, for now I'm rolling with the generally unsatisfactory solution of

$> git config --global --add safe.directory *

[jameper]

I downgraded from VS Enterprise 2022 to VS Professional 2022 and I get this error.
Running my new version of VS as Administrator fixed this issue for me

[die4teoffenbarung]

I actually received this same issue outside of VSCode, running a simple 'git status' on my local Git repository.
I'm running Git version 2.36.0.windows.1.

Same issue here. A little more research turned up that it's related to a recent git update from 2.35.2 to address CVE-2022-24765.

In my case, I'm working from a network drive, so "just fix the owner" isn't a workable solution.

For posterity, since this was the top hit on Google for it for me, there's some discussion on it here on StackOverflow.

Personally, since I can accept the risk, for now I'm rolling with the generally unsatisfactory solution of

$> git config --global --add safe.directory *

Thank you, I'm working on Encrypted Veracrypt drives and this seems like the only working solution.

Thank you, again! :)

[Quraian]

This happened to me as well after I update to 2.36.1.windows.1 from an old version. The issue has nothing to do with VS Code as far as I know, because the error showed up for me on the terminal.

[msftrncs]

VS Code needs to at least acknowledge the unsafe repository status from GIT instead of indicating 'no repository here, make one?', when making one still won't work.

[wauterm]

I downgraded from VS Enterprise 2022 to VS Professional 2022 and I get this error. Running my new version of VS as Administrator fixed this issue for me

This did the trick for me. I normaly always run VS in administrator mode but I forgot to set it up this time.

[Bjoernstjerne]

Had this using windows vscode with repositories in wsl. Switched to vscode WSL.

[lszomoru]

The latest release of VS Code (1.74) contains better handling for git repositories that are being deemed to be unsafe by git.exe due to the ownership of the folder. In this scenario, VS Code will display a tailored message in the "Source Control" view along with an action to mark the repository as safe. I will go ahead and close this issue as resolved, but in case you still have any questions or concerns about this functionality please feel free to reopen the issue. Thanks!