4 ms·
My first thing with SSH is to generate unique keys per machine which never leave that machine (except in backups encrypted with a backup key unique to that mach
by rdl 14y ago
My first thing with SSH is to generate unique keys per machine which never leave that machine (except in backups encrypted with a backup key unique to that machine). If my mba13 gets jacked, I'll be able to revoke all mba13 ssh keys without locking out mbp17 or imac27 or iphone5 or ipad3 keys. This is related to the private keys on same machine" thing you mention.
However, the other reason for segmenting keys is to do agent forwarding.
I might have a CLIENTA key and then allow ssh auth forwarding from a bastion host at CLIENTA to other CLIENTA machines. I also have a CLIENTB key and allow ssh auth forwarding from a bastion host at CLIENTB to other CLIENTB machines. (or, prod/dev at the same company, or personal/work, or whatever).
I don't want anything CLIENTA does on a subverted bastion host or other host to be able to affect CLIENTB in any way.
I also keep some keys totally offline (to manage logging servers, which are normally read-only); ideally with some better way to do 2 party control as well.