News for hackers. Stuff that matters.
Re:After a ten-year hiatus, NetHack 3.6 by pmoriarty on Monday December 07, 2015 @10:23PM (#10694577)
What are some good ways to protect against that?

My first thought is to create an entry in my ~/.ssh/config with an entry for the untrusted host I'm going to ssh in to, using the "IdentityFile" keyword to point to some bogus/misleading identity file. How does that sound?

Re:After a ten-year hiatus, NetHack 3.6 by marklgr on Tuesday December 08, 2015 @04:09AM (#10695463)
In your .ssh/config file:

    Host *
    # Do not send pubkey to each and any host
    PubkeyAuthentication no
    # Use Agent
    IdentitiesOnly       yes
Then override 'PubkeyAuthentication' to yes for each known server you want to connect to.
Re:After a ten-year hiatus, NetHack 3.6 by placeybordeaux on Monday December 07, 2015 @10:28PM (#10694588)
A simple solution would be to create a dummy account and use that for sshing into untrusted hosts.
Re:After a ten-year hiatus, NetHack 3.6 by voltagex_ on Tuesday December 08, 2015 @12:14AM (#10694943)
I wonder if you can turn off automatic use of public keys for "*", and then enable it in .ssh/config on an as-needed basis.
Re:After a ten-year hiatus, NetHack 3.6 by andreabedini on Tuesday December 08, 2015 @03:15AM (#10695339)
Totally possible, I do this. Also I have a different key per host (using %h in IdentityFile)
Re:After a ten-year hiatus, NetHack 3.6 by vinceguidry on Tuesday December 08, 2015 @11:02AM (#10697148)
Do you use pass-phrases with your per-host keys? I wanted to do this, but was unable to make it manageable. ssh-agent will only try so many keys before moving on.
Re:After a ten-year hiatus, NetHack 3.6 by andreabedini on Tuesday December 08, 2015 @06:51PM (#10700746)
No, I don't use key pass-phrases.
Re:After a ten-year hiatus, NetHack 3.6 by alexbecker on Tuesday December 08, 2015 @12:24AM (#10694973)
Just use a different key for github than for everything else. You can specify this in your ssh config using the IdentityFile directive.