-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Chad and Doria Skinner wrote:
>> Ah. Seems to be that you're using ssh protocol 2 (which is good) but >> using an ssh protocol 1 key. Try generating your key with the flag >> '-t dsa'. (I'm sure -d used to attain this result; looks like it >> changed.) I don't think this had anything to do with this poster's problem; he's just using the wrong key type. But to answer your question ... >Unless they have changed things in the new versions Yes. >the ssh v2 keys will need to be placed in authorized_keys2 will they >not? Not in the long run. That will continue to work for awhile, but in some future version, authorized_keys2 will be treated as read-only, and ultimately only authorized_keys will be consulted. See the release notes at http://www.openssh.org for more info. Cheers -d - -- David Talkington PGP key: http://www.prairienet.org/~dtalk/0xCA4C11AD.pgp - -- http://setiathome.ssl.berkeley.edu/pale_blue_dot.html -----BEGIN PGP SIGNATURE----- Version: PGP 6.5.8 Comment: Made with pgp4pine 1.75-6 iQA/AwUBPHHJ2L9BpdPKTBGtEQIqUwCeJf/cIm12H4bms0jvoVHQQUujMZYAoM/k kyYhTG9Tnx+cBgS21Dgb2JlV =8Xf9 -----END PGP SIGNATURE----- _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
