The same holds true in multi-user setups running Windows, as C:\ is writable to every authenticated user by default. Merely navigating to such a space with a Git-enabled PS1 when there is a maliciously-crafted /scratch/.git/ can lead to a compromised account. in computer pools of educational institutes to have a "scratch" space: a mounted disk with plenty of space that is regularly swiped where any authenticated user can create a directory to do their work. It poses a security risk to search for a git directory outside of the directories owned by the current user.įor example, it is common e.g. (Merged by Junio C Hamano - gitster - in commit f1b50ec, ) setup_git_directory(): add an owner check for the top-level directory See commit 6e7ad1e () by Carlo Marcelo Arenas Belón ( carenas). This all comes from With Git 2.35.2 (Q1 2022):
Git windows fix runningsomeoneelse scode vulnerability upgrade#
Or upgrade to 2.5.3 (see below), and opt-out with safe.directory=* To the runtime-prefix, but now these need to be prefixed with We used to interpret paths starting with a single / as relative On Windows, an absolute POSIX path needs to be turned into a Windows Or downgrade Git for Windows (if you really do not want to see this warning), since this message comes from the recent commit 66a6bcf for v2.35.2.windows.1: mingw: deprecate old-style runtime-prefix handling in interpolate_path() Input it via git config produce something like \\\\192.168.1.120\\sambashare in the config file, which is not recognized.Ĭorrect form, as illustrated in michaelosthege's answer is adding %(prefix)/ (not just %(prefix)) before the path: %(prefix)///192.168.1.120/x
Trying instead the UNC path \\192.168.1.120\sambashare\x would result, as commente by the OP LNseyJt2X-24UJ4r7KTL, in: fatal: bad config output. That warning is specific to git-for-windows/git path.c, for any path starting with /
0 kommentar(er)
