4 ms·
Lots of people end up with AgentForward on by default as a sort of "make it work" fix, and lots of people use `git+ssh` on untrusted servers. Here's an example:
by justsomeadvice0 3y ago
Lots of people end up with AgentForward on by default as a sort of "make it work" fix, and lots of people use `git+ssh` on untrusted servers. Here's an example:
https://abyssdomain.expert/@filippo/109659699817863532 https://abyssdomain.expert/@filippo/109659699817863532
TBF this is a vulnerable config either way; but RCE on the client shouldn't be possible.
- tinus_hn 3y agoI’m not so sure git is secure against a malicious server, even if you’re not simply pulling in a Makefile written by the attacker.
- themoonisachees 3y agoAssuming you do perfect integrity checks of the git repo you're pulling, git uses SSH and obeys ssh config for each hosts under the hood. It's safe to say that if you have forward-agent enabled git is vulnerable.
- doubled112 3y agoI've been using a separate SSH config for git for a long time now. Nice to see it wasn't just paranoia. Among the settings are explicitly disabling agent forwarding, and using a git specific identity (SSH key).