[ale] ssh authorized_keys2, what am I missing?

Michael B. Trausch fd0man at gmail.com
Wed Jun 8 13:53:05 EDT 2005


-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

Jason Day wrote:
> On Wed, Jun 08, 2005 at 01:18:08PM -0400, Michael B. Trausch wrote:
> 
>>	(a) You're putting the public key in .ssh/authorized_keys2
>>	(b) .ssh/authorized_keys2 hard linked with .ssh/authorized_keys
> 
> 
> I can never remember when to use authorized_keys vs. authorized_keys2.
> I just checked the ssh man page, and it says:
> 
>     The file $HOME/.ssh/authorized_keys lists the public keys that are
>     permitted for logging in.
> 
> There is no mention of authorized_keys2.  This is for openssh 3.9_p1.
> Maybe authorized_keys2 is no longer used, or specific to ssh.com?
>

They're sometimes used and sometimes not.

The best solution is to hardlink them together.

And someone pointed out that the .ssh directory should be 0700, they are
correct.  I think I wrote 0600.... I haven't finished waking up yet, a
directory is virtually useless to a human if you don't have x permission
on it.

	- Mike
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFCpy4CPXInbkqM7nwRA/7jAKCd4y6r6QcK56nI5EPPCTtIzhDZ1QCeML0c
di10yE4G86cIK249tsREIJM=
=JNR8
-----END PGP SIGNATURE-----



More information about the Ale mailing list