News for hackers. Stuff that matters.
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:

    Host *
        # Disable SSHv1
        RSAAuthentication no

        # Only use a key explicitely provided by an IdentityFile directive
        IdentitiesOnly yes

        # %h expands to the hostname, and %u to the username
        IdentityFile ~/.ssh/%h/%u.key
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.
Re:Being privacy-aware in 2016 by josho on Monday June 06, 2016 @04:19PM (#11849965)
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!