我已经能够在我的ubuntu，fedora核心和mac系统上设置SSHauthentication密钥，但是，我无法使用SSH密钥与redhat enterprise linux 5（RHEL5）正常工作。 我试过用2048位encryption创build密钥，但似乎没有任何工作。 这里是我尝试通过我的mac osx豹（10.5.7）连接时得到的debugging输出。
我检查了权限，我无法弄清楚…谢谢
更新：我已经加倍检查我的权限，他们是0700的.ssh和0600的.ssh / authorized_keys
royrico@mac ~ $ ssh -vv linuxbox OpenSSH_5.1p1, OpenSSL 0.9.7l 28 Sep 2006 debug1: Reading configuration data /etc/ssh_config debug2: ssh_connect: needpriv 0 debug1: Connecting to linuxbox [192.168.2.3] port 22. debug1: Connection established. debug1: identity file /Users/royrico/.ssh/identity type -1 debug2: key_type_from_name: unknown key type '-----BEGIN' debug2: key_type_from_name: unknown key type '-----END' debug1: identity file /Users/royrico/.ssh/id_rsa type 1 debug1: identity file /Users/royrico/.ssh/id_dsa type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_4.3 debug1: match: OpenSSH_4.3 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_5.1 debug2: fd 3 setting O_NONBLOCK debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 debug2: kex_parse_kexinit: ssh-rsa,ssh-dss debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour128,arcfour256,arcfour,aes192-cbc,aes256-cbc,[email protected],aes128-ctr,aes192-ctr,aes256-ctr debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour128,arcfour256,arcfour,aes192-cbc,aes256-cbc,[email protected],aes128-ctr,aes192-ctr,aes256-ctr debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,[email protected],hmac-ripemd160,[email protected],hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,[email protected],hmac-ripemd160,[email protected],hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: none,[email protected],zlib debug2: kex_parse_kexinit: none,[email protected],zlib debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: first_kex_follows 0 debug2: kex_parse_kexinit: reserved 0 debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 debug2: kex_parse_kexinit: ssh-rsa,ssh-dss debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour128,arcfour256,arcfour,aes192-cbc,aes256-cbc,[email protected],aes128-ctr,aes192-ctr,aes256-ctr debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour128,arcfour256,arcfour,aes192-cbc,aes256-cbc,[email protected],aes128-ctr,aes192-ctr,aes256-ctr debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,hmac-ripemd160,[email protected],hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,hmac-ripemd160,[email protected],hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: none,[email protected] debug2: kex_parse_kexinit: none,[email protected] debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: first_kex_follows 0 debug2: kex_parse_kexinit: reserved 0 debug2: mac_setup: found hmac-md5 debug1: kex: server->client aes128-cbc hmac-md5 none debug2: mac_setup: found hmac-md5 debug1: kex: client->server aes128-cbc hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug2: dh_gen_key: priv key bits set: 138/256 debug2: bits set: 493/1024 debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug1: Host 'linuxbox' is known and matches the RSA host key. debug1: Found key in /Users/royrico/.ssh/known_hosts:1 debug2: bits set: 504/1024 debug1: ssh_rsa_verify: signature correct debug2: kex_derive_keys debug2: set_newkeys: mode 1 debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug2: set_newkeys: mode 0 debug1: SSH2_MSG_NEWKEYS received debug1: SSH2_MSG_SERVICE_REQUEST sent debug2: service_accept: ssh-userauth debug1: SSH2_MSG_SERVICE_ACCEPT received debug2: key: /Users/royrico/.ssh/identity (0x0) debug2: key: /Users/royrico/.ssh/id_rsa (0x107ea0) debug2: key: /Users/royrico/.ssh/id_dsa (0x0) debug1: Authentications that can continue: publickey,gssapi-with-mic,password debug1: Next authentication method: publickey debug1: Trying private key: /Users/royrico/.ssh/identity debug1: Offering public key: /Users/royrico/.ssh/id_rsa debug2: we sent a publickey packet, wait for reply debug1: Authentications that can continue: publickey,gssapi-with-mic,password debug1: Trying private key: /Users/royrico/.ssh/id_dsa debug2: we did not send a packet, disable method debug1: Next authentication method: password royrico@linuxbox's password: 检查你的~/.ssh/authorized_keys文件的权限。 他们应该是0600 。
% chmod 0700 .ssh % chmod 0600 .ssh/authorized_keys
是我的标准模式
更新：检查您的主目录是否由您独自拥有，请确保您的主要组没有对主目录的写入权限。 有一个附加向量，在你的主组中的某个人可以移动你的.ssh目录，如果他们有写入权限的$HOME的根目录
debug2: key_type_from_name: unknown key type '-----BEGIN' debug2: key_type_from_name: unknown key type '-----END'
这些消息看起来很重要。 看起来你的身份文件中有错误的密钥types。
当您生成密钥对时，通常会有一个名为id_rsa.pub或id_dsa.pub的公钥。 该文件的内容是粘贴到远程服务器上的authorized_keys文件中的内容。 仔细检查一下，以确保您将公钥的一半添加到authorized_keys中。
私钥通常与公钥相同，但没有.pub扩展名，例如id_rsa或id_dsa。 也许你的本地系统找不到正确的私钥使用？ 试试ssh -i /path/to/private/key linuxbox 。
它不应该超过（例如）
ssh-keygen -t rsa ssh-copy-id -i ~/.ssh/id_rsa.pub [email protected] ssh-copy-id -i ~/.ssh/id_rsa.pub [email protected] ssh-copy-id -i ~/.ssh/id_rsa.pub [email protected]
哼，快问你的selinux设置如何？ getenforce说什么？ 如果你还没有停用selinux，也许你可以看看/var/log/audit.log并使用audit2why： http : //linux.die.net/man/8/audit2why
或者你也可以停用selinux，编辑/ etc / sysconfig / selinux
希望这可以帮助