![]() The first it finds is the one from /home/tommy/.git. If mary, by mistake, where to execute git in her directory, but outside of her phone_app project, then old git would go up the directory tree to search a. In this case, the user tommy owns his own directory under /home, but (for some reason) rents out space to other users, in this case mary and anthony. Lets look at the following simple directory structure. Going through the post about the vulnerability again after a good night's sleep, I think a bit of clarification is in order. Running git config -global -add safe.directory /opt/flutter did indeed fix the problem for me. I am not working as root, thus I run into the same problem. I ran into the same problem using flutter on Linux, which on my distro was installed in /opt/flutter. git folder (the git repository) is the issue.Ĭloning the project anew is a platform independent way to make sure you are the owner. The update is only a few hours old, so I guess things are still in flux.įor now, as the message from git suggests, execute git config -global -add safe.directory F:/GitHub/my-projectĪnd make sure you are calling git from within F:/GitHub/my-project for now.ĮDIT: As we found out in the comments below, the owner of the parent of the directory containing the. Is the user you're currently logged in with also the owner of the folder?Īlso, are you invoking git from within the repository directory? I think it has less to do with your email, and more with the owner of the directories on your filesystem. This seems to be related to this announcement of a vulnerability: Git config -global -add safe.directory "*" However, if you are the sole user of your machine 100% of the time, and your repositories are stored locally, then disabling this check should, theoretically, pose no increased risk.Īlso note that you can't currently combine this with a file path, as the command doesn't interpret the wildcard * as an operator per say– it just takes the "*" argument to mean "disable safe repository checks/ consider all repositories as safe".ġ - If this fails in your particular terminal program in Windows, try surrounding the wildcard with double quotes instead of single (Via this GitHub issue): You should not do this if your repositories are stored on a shared drive. gitconfig file: īefore disabling, make sure you understand this security measure, and why it exists. It will add the following setting to your global. Git config -global -add safe.directory '*' 1 Start: Run in container: rm '/tmp/vscode-ssh-auth-f14e26ae6cafba7effb631d3b4a38ab2850d6897.sock' & ln -s '/tmp/vscode-ssh-auth-d8029642a82b8c4609319691951157654c82cb55.sock' '/tmp/vscode-ssh-auth-f14e26ae6cafba7effb631d3b4a38ab2850d6897.Starting in Git v2.35.3, safe directory checks can be disabled, which will end all the "unsafe repository" errors (this will also work in the latest patch versions of 2.30-34). Start: Run in container: cat /proc/711/environ Port forwarding 52364 > 34805 > 34805 stderr: Connection established ![]() Port forwarding connection from 52364 > 34805 > 34805 in the container. Port forwarding 52360 > 34805 > 34805 stderr: Connection established Port forwarding connection from 52360 > 34805 > 34805 in the container. Start: Run: docker version -format f' || true ![]() Setting up container for folder or workspace: /home/julian/repo/EmbeddedC/4q
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |