Originally Posted by AndrewSerk
Old habits, Please disregard my above post.
There is no reason to disregard or retract it. It's merely a method that has an obvious security implication that JP' describes. That doesn't make it an unusable method.
Originally Posted by cdgary
I'm aware of all of that. My post discusses issues I was having with a permanent automatic ssh login without using the passphrase key.
You need to describe exactly what you mean - b/c you are making up terms.
'passphrase key' is meaningless. Keygen utility is used to create bother user and host keys. Your user account key can have a passphrase associated with it. In that case authentication requires two pieces of information - the other half-key and the passphrase.
If you create a key w/o a passphrase as AndrewSerk suggests then no passphrase - not even a null passphrase will be requested.
So you can do this ....
[stevea@crucibulum Desktop]$ ssh hypoxylon
Last login: Fri Dec 23 04:08:41 2011 from crucibulum.localdomain
[stevea@hypoxylon ~]$ ssh lycoperdon
Last login: Wed Dec 21 09:49:59 2011
with no password or passphrase authentication.
Next - your meaning of "permanent automatic ssh login".
The putting the public half-key into ~/.ssh/authorized_hosts means the PubkeyAuthentication scheme can be use for authentication. That seems like 'permanent' to me.
There is no 'automatic' login per se. You either type "ssh me@somehost" or you can cause a window to appear that does this at login.