[długie] ssh i autoryzacja przez publickey

Marcin Wojtczuk (FastViper) fastviper w poczta.onet.pl
Nie, 1 Wrz 2002, 15:53:11 CEST


$ ssh-keygen -t rsa

$  cd .ssh; ls
id_rsa  id_rsa.pub

$ ncftp ftp://viper@uplink
User viper logged in.
Logged in to 192.168.0.1.
ncftp / > cd .ssh
ncftp /.ssh > mput -z id_rsa.pub authorized_keys

$ ssh uplink -2 -i ~/.ssh/id_rsa -vvv
OpenSSH_3.2.3p1, SSH protocols 1.5/2.0, OpenSSL 0x0090602f
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug1: Rhosts Authentication disabled, originating port will not be trusted.
debug1: restore_uid
debug1: ssh_connect: getuid 500 geteuid 500 anon 1
debug1: Connecting to uplink [192.168.0.1] port 22.
debug1: temporarily_use_uid: 500/1000 (e=500)
debug1: restore_uid
debug1: temporarily_use_uid: 500/1000 (e=500)
debug1: restore_uid
debug1: Connection established.
debug3: Not a RSA1 key file /home/users/viper/.ssh/id_rsa.
debug2: key_type_from_name: unknown key type '-----BEGIN'
debug3: key_read: no key found
debug3: key_read: no space
[ciach, kilka razy tak]
debug3: key_read: no space
debug2: key_type_from_name: unknown key type '-----END'
debug3: key_read: no key found
debug1: identity file /home/users/viper/.ssh/id_rsa type 1
debug1: Remote protocol version 2.0, remote software version OpenSSH_3.2.3p1
debug1: match: OpenSSH_3.2.3p1 pat OpenSSH*
Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_3.2.3p1
[ciach, ciphers]
debug1: authentications that can continue: publickey,password,keyboard-interactive
debug3: start over, passed a different list publickey,password,keyboard-interactive
debug3: preferred publickey,keyboard-interactive,password
debug3: authmethod_lookup publickey
debug3: remaining preferred: keyboard-interactive,password
debug3: authmethod_is_enabled publickey
debug1: next auth method to try is publickey
debug1: try pubkey: /home/users/viper/.ssh/id_rsa
debug3: send_pubkey_test
debug2: we sent a publickey packet, wait for reply
debug1: input_userauth_pk_ok: pkalg ssh-rsa blen 149 lastkey 0x8093768 hint 0
debug2: input_userauth_pk_ok: fp 2d:70:5f:3a:62:c7:65:6d:f3:a2:7c:a6:c3:9b:66:81
debug3: sign_and_send_pubkey
debug1: read PEM private key done: type RSA
debug1: authentications that can continue: publickey,password,keyboard-interactive
debug2: we did not send a packet, disable method
debug3: authmethod_lookup keyboard-interactive
debug3: remaining preferred: password
debug3: authmethod_is_enabled keyboard-interactive
debug1: next auth method to try is keyboard-interactive
debug2: userauth_kbdint
debug2: we sent a keyboard-interactive packet, wait for reply
debug1: authentications that can continue: publickey,password,keyboard-interactive
debug3: userauth_kbdint: disable: no info_req_seen
debug2: we did not send a packet, disable method
debug3: authmethod_lookup password
debug3: remaining preferred:
debug3: authmethod_is_enabled password
debug1: next auth method to try is password
viper w uplink's password:



Dlaczego nie działa jak powinno ? Powinien mnie autoryzować 
na podstawie klucza a chce koniecznie hasło. Co mogłem schrzanić ?

[root w uplink ssh]# grep ^RSA sshd_config
RSAAuthentication yes
[root w uplink ssh]# grep ^RSA ssh_config

Nie mam własnego pliku config do ssh nigdzie.

Help ? :)
-- 
[ FastViper ] [ http://www.stringi.com/viper/ ]
słońce zachodzi, minął kolejny dzień a po wyścigu dobrze zabawić się..



Więcej informacji o liście dyskusyjnej pld-users-pl