3 ms·
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 s
by pmoriarty 11y ago
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?
- placeybordeaux 11y agoA simple solution would be to create a dummy account and use that for sshing into untrusted hosts.
- voltagex_ 11y agoI wonder if you can turn off automatic use of public keys for "*", and then enable it in .ssh/config on an as-needed basis.
- andreabedini 11y agoTotally possible, I do this. Also I have a different key per host (using %h in IdentityFile)
- vinceguidry 11y agoDo 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.
- andreabedini 11y agoNo, I don't use key pass-phrases.
- deleted 11y ago[deleted]
- deleted 11y ago[deleted]
- alexbecker 11y agoJust use a different key for github than for everything else. You can specify this in your ssh config using the IdentityFile directive.
- marklgr 11y agoIn 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.