Исходное сообщение
"Проблема с sshd" Отправлено kran, 31-Авг-07 14:27
>Определись где находится ".ssh/authorized_keys", обычно папка .ssh расположена в домашнем каталоге пользователя, >если это так следуем писать "~/.ssh/authorized_keys" это я просто не дописал. authorized_keys находится в домашнем каталоге в подпапке .ssh Вот отладочная информация если поможет OpenSSH_3.5p1, SSH protocols 1.5/2.0, OpenSSL 0x0090701f debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: Rhosts Authentication disabled, originating port will not be trusted. debug1: ssh_connect: needpriv 0 debug1: Connecting to 10.10.10.132 [10.10.10.132] port 22. debug1: Connection established. debug1: identity file id_rsa type 1 debug1: Remote protocol version 2.0, remote software version OpenSSH_3.5p1 debug1: match: OpenSSH_3.5p1 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_3.5p1 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server->client aes128-cbc hmac-md5 none debug1: kex: client->server aes128-cbc hmac-md5 none debug1: dh_gen_key: priv key bits set: 137/256 debug1: bits set: 506/1024 debug1: sending SSH2_MSG_KEXDH_INIT debug1: expecting SSH2_MSG_KEXDH_REPLY debug1: Host '10.10.10.132' is known and matches the DSA host key. debug1: Found key in /root/.ssh/known_hosts:1 debug1: bits set: 496/1024 debug1: ssh_dss_verify: signature correct debug1: kex_derive_keys debug1: newkeys: mode 1 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: userauth_pubkey_agent: testing agent key /root/.ssh/id_rsa debug1: authentications that can continue: publickey,password debug1: try pubkey: id_rsa debug1: authentications that can continue: publickey,password debug1: next auth method to try is password root@10.10.10.132's password: