4 ms·
> You can invoke git-who as git who by setting up an alias in your global Git config This works even without the alias, by the way: by default `git whatever` w
by mmcclimon 2y ago
> You can invoke git-who as git who by setting up an alias in your global Git config
This works even without the alias, by the way: by default `git whatever` will search your path for `git-whatever` and execute it.
- weebst 2y agoWow! I had no idea. Will need to update the README. Thanks for the tip!
- jeff_carr 1y agoYes, that is awesome. I wonder if "go" works like that also?
- chatmasta 2y agoHas this behavior been the source of exploits in the past? Something about it feels dangerously presumptuous to me.
- mdaniel 2y agoI am guessing it only resorts to that expansion if it dosesn't _already_ know about the command, because $(printf '#!/bin/sh\necho pwned\n' > /bin/git-status; chmod 755 /bin/git-status; git status) results in the thing happening that you'd expect, not a mysterious message FWIW, both brew and kubectl also have adopted this behavior (of $(basename)-plugin style verb extensions) so I find it unlikely they'd all do it if it was a straight-up facepalm
- igorbark 2y agoprobably adding a confirmation message the first time the alias is used for each command would be good, it would be nice to know when i'm invoking git and when i'm invoking a third party binary regardless of any exploit attempts!
- account42 1y agoIf malicious code ends up in your $PATH you have much bigger problems than git having a seamless plugin architecture.