Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Access denied for files under Git repositories after migration to Git 2.25.0.windows.1 #2500

Closed
frederic-meyrou opened this issue Jan 30, 2020 · 3 comments

Comments

@frederic-meyrou
Copy link

Context : I use git to maintain and deploy portable tools under many windows target servers.

Under Windows server 2K8 / 2K12 / 2K16 or Windows 7/10 all my repositories get corrupted after I pull in certain conditions just after I did the migration to latest Windows git client to cover a CVE.

Files rights get a strange "NULL SID" and the other windows users have incorrect permissions.
This impact all staged files but also the .git folder, for example the ".git\config" file.

This leads for application using thoses files to "Access denied".

The only way to fix the problem is to delete everything and clone again the repository from the server.

@dscho
Copy link
Member

dscho commented Jan 30, 2020

Under Windows server 2K8 / 2K12 / 2K16 or Windows 7/10 all my repositories get corrupted after I pull in certain conditions just after I did the migration to latest Windows git client to cover a CVE.

Files rights get a strange "NULL SID" and the other windows users have incorrect permissions.
This impact all staged files but also the .git folder, for example the ".git\config" file.

What "certain conditions" would those be?

@frederic-meyrou
Copy link
Author

Dear,
You can close the issue, I found another Git version included in CygWin was messing up in my PATH and giving the above result, version 2.25.0 is not the faulty guy.
Sorry for this post.
./Fred

@dscho
Copy link
Member

dscho commented Feb 1, 2020

Ah, good to know! Thanks for adding the detail so I don't have to worry about this ticket any further.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants