5 ms·
Yeah, dang updated the link: https://news.ycombinator.com/item?id=31010550 https://news.ycombinator.com/item?id=31010550 (it was previously https://github.com/g
by wolfgang42 5y ago
Yeah, dang updated the link: https://news.ycombinator.com/item?id=31010550 https://news.ycombinator.com/item?id=31010550 (it was previously https://github.com/git/git/commit/8959555cee7ec045958f9b6dd62e541affb7e7d9 https://github.com/git/git/commit/8959555cee7ec045958f9b6dd6...)
- ineptech 5y agoThank you, I was confused. I'm very curious if the people complaining about this change as being too paternalistic still feel that way after reading the full disclosure link.
- SpicyLemonZest 5y agoEven after reading the full disclosure link, I'm pretty surprised to learn that a security boundary was intended here. I thought it was common knowledge that git did an uncontrolled search up the filesystem for a .git file, and it would never have occurred to me to run git on a machine where people I don't trust have write access.
- Dylan16807 5y agoI was vaguely aware that git would search for .git directories. I had no idea that "git status" would run commands from such a directory.