-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jussi Ekholm <[EMAIL PROTECTED]> wrote:
(Replying to myself, sorry - just trying to provide extra information) > Dietmar Goldbeck <[EMAIL PROTECTED]> wrote: >> On Sat, Jun 22, 2002 at 02:20:20AM -0500, Rob VanFleet wrote: >> It is very difficult to help you without error messages, since there >> shouldn't be a problem. openssh 3.0.2 and 3.2.3 play perfectly well >> with each other. > > I'm having similar problem, only difference being different SSH > softwares between two systems. My end has OpenSSH 3.4: [...] > And the other system has: > ssh: SSH Secure Shell 3.0.1 (non-commercial version) > > I'm actually quite ignorant with SSH Communications Security Corp's SSH, > so could someone guide me a bit? I tried generating RSA key with > 'ssh-keygen -t rsa -N ""' and copying it to this remote server to > directory ~/.ssh/authorized_keys2. But then I noticed, that the remoted > SSH uses ~/.ssh2 and I tried to look up the FILES section of SSH2(1), > for no avail. After I created a key with 'ssh-keygen -t dsa -N ""' and copied it to the remote server with 'ssh-copy-id', I connected to the server. And again, for no surprise, I got password prompt. This is what I got with 'ssh -v': debug1: SSH2_MSG_NEWKEYS sent debug1: waiting for SSH2_MSG_NEWKEYS debug1: newkeys: mode 0 debug1: SSH2_MSG_NEWKEYS received debug1: done: ssh_kex2. debug1: send SSH2_MSG_SERVICE_REQUEST debug1: service_accept: ssh-userauth debug1: got SSH2_MSG_SERVICE_ACCEPT debug1: authentications that can continue: publickey,password debug1: next auth method to try is publickey debug1: try pubkey: /home/ekhowl/.ssh/id_dsa debug1: authentications that can continue: publickey,password debug1: try pubkey: /home/ekhowl/.ssh/id_rsa debug1: authentications that can continue: publickey,password debug1: try pubkey: /home/ekhowl/.ssh/id_dsa debug1: authentications that can continue: publickey,password debug1: try pubkey: /home/ekhowl/.ssh/id_rsa debug1: authentications that can continue: publickey,password debug1: next auth method to try is password I'm not an expert with SSH, so I don't even know if I pasted enough from the output. :-) If I missed something, please let me know... >> Try generating new keys for protocol 2 with "ssh-keygen -d", >> copy them with "ssh-copy-id" and try again. > > What does option '-d' for ssh-keygen do? Apparently identical to 'ssh-keygen -t dsa'. - -- Jussi Ekholm -- [EMAIL PROTECTED] -- http://erppimaa.ihku.org/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9HTc3AtEARxQQCB4RAiw0AKCa/t0vtsSnpNnGFF3JZPuvG5B5/ACgpZ4f 1gDNjDe9pGxf+2uJXLRlDag= =3KXd -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
