You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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
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.
The text was updated successfully, but these errors were encountered: