News for hackers. Stuff that matters.
Re:More Git and GitHub Secrets by txutxu on Thursday July 25, 2013 @05:58AM (#6101671)
No. But it eases "man in the middle" attacks (someone impersonating the host you think you're connecting to, with that key).

Still, if someone puts your pub key in an authorized_keys of a malicious host, and then manipulates your DNS or ARP to conduct you to such host, you should get some SSH warnings about the host fingerprint, etc.

And still, if you're using a dedicated key, the only possible attack could be to make you commit your repo changes, to the malicious machine instead of to github.

Re:More Git and GitHub Secrets by inopinatus on Thursday July 25, 2013 @06:32AM (#6101742)
This is also the reason not to forward your ssh-agent (in my view, one of the most poorly considered features of ssh).
Re:More Git and GitHub Secrets by dlitz on Friday July 26, 2013 @05:22AM (#6107281)
If agent-forwarding wasn't implemented, more people would just copy their private keys to several machines.

At least when you use agent forwarding, your key is only exposed while you're actually connected to the machine.