-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Matthew Simpson wrote:
>>>ssh-keygen of A, this created 2 files .shh/identity and >>>.ssh/identity.pub. Then I scp .ssh/indentity.pub to >>>.ssh/authorized-keys on machine B. When I tried sshing from A to B I >>>still get promt for passwd >>>debug1: got SSH2_MSG_SERVICE_ACCEPT >>>debug1: authentications that can continue: publickey,password >>>debug1: next auth method to try is publickey >>>debug1: try privkey: /home/msimpson/.ssh/id_rsa >>>debug1: try privkey: /home/msimpson/.ssh/id_dsa >>>debug1: next auth method to try is password >> >>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.) >On Machine A the openssh vers is openssh-2.5.2p2-5 which uses the >ssh-keygen -t option but on machine B the vers is openssh-2.1.1p4-1 > >[root@B /root]# ssh-keygen -d dsa >Too many arguments. >Usage: ssh-keygen [-lpqxXydc] [-b bits] [-f file] [-C comment] [-N >new-pass] [-P pass] > >Any clues? If I just create a rsa1 key and use ssh -1 i works no probs. Older versions (still works in 3.0.2, but not documented): $ ssh-keygen -d Newer versions: $ ssh-keygen -t dsa One of the above will give you a dsa key, called (by default) id_dsa. But the biggest problem you currently have is 2.1.1 accepting protocol 1. You're asking to be rooted. Update it pronto, and turn off v.1. - -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/AwUBPHG3a79BpdPKTBGtEQJ3XACeKpAMJ3o7qk0tJByMY/A/jeoGUEMAoORQ qmVX6aV7NlfEV6p4/UYZu3VF =HPc8 -----END PGP SIGNATURE----- _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
