Hi Joseph, 

> Why not just use authorized_keys with an empty pass phrase?

because every responsible system admin will immediately kill you when you do 
that? :-)

Except in very specific situations, e.g. unattended jobs that copy data or 
execute commands over ssh connections, it is very unwise to *ever* create an 
ssh key without a passphrase, as the only thing between that key and access to 
the systems it 'protects' is then file permissions on the server it is located 
on. 

Even in the few situations where it is unavoidable (in most cases it just seems 
so) to use an unprotected key, actions should be taken to limit its usability 
as much as possible (no-pty, forced commands etc.). 

The sensible way to achieve what the OP wants is to use an SSH agent.

Cheers, 

  Peter.

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail

_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Reply via email to