News for hackers. Stuff that matters.

A comment on How Not to copy your SSH private key to your servers. Parent comment

Re:How Not to copy your SSH private key to your servers by danieldon on Monday April 19, 2010 @02:05PM (#1277407)
I feel like I'm missing something here. Why would someone copy around a single private key instead of generating a new key pair for each user@host?
[ Parent | on HN ]
Re:How Not to copy your SSH private key to your servers by ars on Monday April 19, 2010 @03:43PM (#1277642)
You don't need to generate a new keypair - just copy your (single) public key to the authorized_keys file on each machine.

I can't think of any reason at all to copy the private key though.

[ Parent | on HN ]
Re:How Not to copy your SSH private key to your servers by dedward on Monday April 19, 2010 @07:23PM (#1278148)
No that's backwards - the reason is laziness.

Sysadmin has two worksations - say a laptop and a desktop. He wants to SSH into all his remote boxen from either. The default reaction might be to just copy his already-authorized private key to his other machine just for ease of use - the proper solution would be to generate a new keypair on the new machine and then copy it to the required remote machines as well, so either can be revoked and tracked separately.

[ Parent | on HN ]