How Not to copy your SSH private key to your servers

Re:How Not to copy your SSH private key to your servers by mbreese on Monday April 19, 2010 @11:26AM (#1276902)

Unless you want to use headless logins...

An example would be a cron job that copies files to a backup server via scp or rsync over ssh. However, this should also be accompanied by host filters in the authorized_keys file to restrict access to specific hosts.

Using pastebin for this is wrong on so many levels.

[ Parent | on HN ]

Re:How Not to copy your SSH private key to your servers by jsn on Monday April 19, 2010 @12:33PM (#1277093)

For obvious reasons, you're much better off generating a new keypair for that (not reusing any existing private keys).

[ Parent | on HN ]

Re:How Not to copy your SSH private key to your servers by barrkel on Monday April 19, 2010 @12:25PM (#1277068)

Automating ssh, however, is surprisingly painful.

[ Parent | on HN ]

Re:How Not to copy your SSH private key to your servers by rcoder on Monday April 19, 2010 @07:53PM (#1278199)

This is why Net::SSH and Paramiko are so wonderful. Using the OpenSSH binaries through a pair of pipes is certainly a pain, but if you grok the protocol, either of those libraries can make it really easy to wire up secure pipes between machines.

[ Parent | on HN ]

Re:How Not to copy your SSH private key to your servers by danieldon on Monday April 19, 2010 @02:20PM (#1277445)

Why wouldn't you just generate a new key pair?

[ Parent | on HN ]

Re:How Not to copy your SSH private key to your servers by wizard_2 on Monday April 19, 2010 @12:37PM (#1277108)

With python you have Fabric and paramiko which makes automating ssh very strait forward.

[ Parent | on HN ]