Re:Being privacy-aware in 2016
by radialbrain on Monday June 06, 2016 @12:13PM
(#11847841)
The solution to that is to use the IdentityFile directive in your ~/.ssh/config with username / hostname expansion.
I use:
This ensures that at most one key is used, and prevents me from having to modify my config every time I generate a key for a new host.
[ Parent
| on HN ]
The point remains, there isn't much benefit to using a different key per host. What attack vector is this extra effort protecting you from?
Re:Being privacy-aware in 2016
by georgehotelling on Monday June 06, 2016 @01:12PM
(#11848371)
Awesome, I did not realize you could use filename templates for SSH keys. Thanks!