Re:After a ten-year hiatus, NetHack 3.6
by 0942v8653 on Monday December 07, 2015 @10:15PM
(#10694542)
Careful when SSHing into an untrusted host. They can find your public key(s) that way and maybe identify who you are on GitHub.
[ Parent
| on HN ]
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.
I don't understand, why is that a bad thing? Maybe it might be an issue if you're trying to do something anonymously (but at that point, you shouldn't be using your regular machine anyway).
It's rather unexpected. Browsers carry so much baggage that you need a private mode, I wouldn't have expected something like ssh to have this sort of problem before I read about how it exposes your keys.
Re:After a ten-year hiatus, NetHack 3.6
by windowsworkstoo on Monday December 07, 2015 @11:11PM
(#10694748)
It's not, it's a "public" key.
Re:After a ten-year hiatus, NetHack 3.6
by Drdrdrq on Tuesday December 08, 2015 @12:17AM
(#10694954)
It's not a problem from security perspective. It is a problem from privacy perspective.
Re:After a ten-year hiatus, NetHack 3.6
by illumen on Tuesday December 08, 2015 @04:38AM
(#10695533)
Privacy is security.
Re:After a ten-year hiatus, NetHack 3.6
by illumen on Tuesday December 08, 2015 @09:38AM
(#10696533)
"Security is the degree of resistance to, or protection from, harm."
"Privacy: a secret matter."
"Privacy: freedom from unauthorized intrusion."
"Privacy: the quality or state of being apart from company or observation."
So you see, privacy IS security.
Re:After a ten-year hiatus, NetHack 3.6
by Drdrdrq on Tuesday December 08, 2015 @01:22PM
(#10698241)
I can't tell if you forgot /s?
Re:After a ten-year hiatus, NetHack 3.6
by craigching on Tuesday December 08, 2015 @09:18AM
(#10696419)
> It's not, it's a "public" key
Not just any public key, it's your public key. It identifies you.
Re:After a ten-year hiatus, NetHack 3.6
by dspillett on Tuesday December 08, 2015 @08:16AM
(#10696109)
If your identity is that sensitive keep a standard public key that is used by default, but for services where you might want your identity to not be linked to other accounts/places/activities have a separate key for each and specified where to use it in you SSH config (or by naming with the -i parameter on each ssh call).
I could be more worried about a modified sshd, that triggers different code paths in the client than the expected ones.
Re:After a ten-year hiatus, NetHack 3.6
by marssaxman on Tuesday December 08, 2015 @01:42PM
(#10698394)
Why would that be a problem?