-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Aaron Konstam wrote:
> On Fri, 2006-07-07 at 12:08 +0800, Man-Chi Leung wrote:
[...]
>> sorry that I am a newbie to fedora FC5, I used to be in Solaris
>> environment. i could not configure correctly for public key ssh
>> login as I used to do in Solaris.
>>
>> my step:
>>
>> 1) cat my public key and put in my
>> $fedora_user/.ssh/authorized_keys
>>
>> 2) configure fedora's /etc/ssh/sshd_config, uncomment the following
>> 2 lines
[...]
> It is not clear to me that you understand that the public key from
> the sending machine (the one issuing the ssh) is put in the
> authorized keys of the targeted machine.
Man-Chi specified that he was putting his public key in the
authorized_keys file for his $fedora_user and then editing the
sshd_config on the Fedora box. This would lead me to believe that
he's trying to login to the Fedora box and that he has put the public
key in the proper place.
> Also where you put it depends of what coding the key was generated
> in. rsa1, rsa or dsa.
Why do you say that? Way back in time ssh would use authorized_keys
for V1 keys and authorized_keys2 for V2 keys, but that hasn't been the
case in years. I don't know if it still checks both files or not, I
would guess it might for backward compatibility but I haven't checked
this.
- --
Todd OpenPGP -> KeyID: 0xD654075A | URL: www.pobox.com/~tmz/pgp
======================================================================
School is the advertising agency which makes you believe that you need
the society as it is.
-- Ivan Illich -- "Deschooling Society"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.4 (GNU/Linux)
Comment: When crypto is outlawed bayl bhgynjf jvyy unir cevinpl.
iG0EARECAC0FAkSufDgmGGh0dHA6Ly93d3cucG9ib3guY29tL350bXovcGdwL3Rt
ei5hc2MACgkQuv+09NZUB1qkpgCg2uMqAK6RR145V8hKg4NyDpy5Fp4Anjs2xJbW
qi05Wg9gVEsK5VoNXkCG
=nAK1
-----END PGP SIGNATURE-----
