kos*_*wag 8 java ssh jsch kotlin private-key
我正在尝试使用 Kotlin + JSch 建立 SSH 连接，但失败并显示
\n\n\ncom.jcraft.jsch.jSchException：身份验证失败
\n
采取的步骤：
\nssh-keygen -t rsa -m PEM使用（OpenSSH 版本OpenSSH_8.2p1：）生成 SSH 密钥对id_rsa.pub到/home/username/.ssh/authorized_keys服务器上的文件中ssh -i /path/to/id_rsa username@example.host.com\xe2\x80\x93 工作正常import com.jcraft.jsch.JSch\n\nconst val USER = "username"\nconst val HOST = "example.host.com"\nconst val IDENTITY = "/path/to/id_rsa"\n\n\nfun main() {\n val jsch = JSch().apply {\n addIdentity(IDENTITY)\n setKnownHosts("/path/to/known_hosts")\n }\n\n jsch.getSession(USER, HOST)\n .connect()\n}\n...失败但有异常：
\nimport com.jcraft.jsch.JSch\n\nconst val USER = "username"\nconst val HOST = "example.host.com"\nconst val IDENTITY = "/path/to/id_rsa"\n\n\nfun main() {\n val jsch = JSch().apply {\n addIdentity(IDENTITY)\n setKnownHosts("/path/to/known_hosts")\n }\n\n jsch.getSession(USER, HOST)\n .connect()\n}\n这里可能有什么问题？
\nJSch日志输出：
\nException in thread "main" com.jcraft.jsch.JSchException: Auth fail\n at com.jcraft.jsch.Session.connect(Session.java:519)\n at com.jcraft.jsch.Session.connect(Session.java:183)\n at MainKt.main(Main.kt:18)\n at MainKt.main(Main.kt)\nssh -vvv输出：
INFO: Connecting to example.host.com port 22\nINFO: Connection established\nINFO: Remote version string: SSH-2.0-OpenSSH_8.9p1 Ubuntu-3\nINFO: Local version string: SSH-2.0-JSCH-0.1.54\nINFO: CheckCiphers: aes256-ctr,aes192-ctr,aes128-ctr,aes256-cbc,aes192-cbc,aes128-cbc,3des-ctr,arcfour,arcfour128,arcfour256\nINFO: CheckKexes: diffie-hellman-group14-sha1,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521\nINFO: CheckSignatures: ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521\nINFO: SSH_MSG_KEXINIT sent\nINFO: SSH_MSG_KEXINIT received\nINFO: kex: server: curve25519-sha256,curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,sntrup761x25519-sha512@openssh.com,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group14-sha256\nINFO: kex: server: rsa-sha2-512,rsa-sha2-256,ecdsa-sha2-nistp256,ssh-ed25519\nINFO: kex: server: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com\nINFO: kex: server: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com\nINFO: kex: server: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1\nINFO: kex: server: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1\nINFO: kex: server: none,zlib@openssh.com\nINFO: kex: server: none,zlib@openssh.com\nINFO: kex: server: \nINFO: kex: server: \nINFO: kex: client: ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group14-sha1,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group1-sha1\nINFO: kex: client: ssh-rsa,ssh-dss,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521\nINFO: kex: client: aes128-ctr,aes128-cbc,3des-ctr,3des-cbc,blowfish-cbc,aes192-ctr,aes192-cbc,aes256-ctr,aes256-cbc\nINFO: kex: client: aes128-ctr,aes128-cbc,3des-ctr,3des-cbc,blowfish-cbc,aes192-ctr,aes192-cbc,aes256-ctr,aes256-cbc\nINFO: kex: client: hmac-md5,hmac-sha1,hmac-sha2-256,hmac-sha1-96,hmac-md5-96\nINFO: kex: client: hmac-md5,hmac-sha1,hmac-sha2-256,hmac-sha1-96,hmac-md5-96\nINFO: kex: client: none\nINFO: kex: client: none\nINFO: kex: client: \nINFO: kex: client: \nINFO: kex: server->client aes128-ctr hmac-sha1 none\nINFO: kex: client->server aes128-ctr hmac-sha1 none\nINFO: SSH_MSG_KEX_ECDH_INIT sent\nINFO: expecting SSH_MSG_KEX_ECDH_REPLY\nINFO: Host \'example.host.com\' is known and matches the ECDSA host key\nINFO: SSH_MSG_NEWKEYS sent\nINFO: SSH_MSG_NEWKEYS received\nINFO: SSH_MSG_SERVICE_REQUEST sent\nINFO: SSH_MSG_SERVICE_ACCEPT received\nINFO: Authentications that can continue: publickey,keyboard-interactive,password\nINFO: Next authentication method: publickey\nINFO: Disconnecting from example.host.com port 22\nException in thread "main" com.jcraft.jsch.JSchException: Auth fail\n at com.jcraft.jsch.Session.connect(Session.java:519)\n at com.jcraft.jsch.Session.connect(Session.java:183)\n at MainKt.main(Main.kt:37)\n at MainKt.main(Main.kt)\nMar*_*ryl 15
您的 OpenSSHssh连接正在使用rsa-sha2-512密钥签名。虽然这并不能证明您的服务器需要它，但很可能需要它。
JSch 不支持rsa-sha2. 由于 JSch 似乎不再更新，它很可能永远不会更新。
JSch 的一个分支可以做到这一点：
\n https://github.com/mwiede/jsch
\n至少对其进行测试，以验证这确实是问题所在。
rsa-sha2另一个（显然不太安全）选项是通过将deprecated ssh-rsa添加到 来重新配置服务器，使其不再需要PubkeyAcceptedAlgorithms.
其他人可能会因为不同的原因而遇到相同的错误。例如，当期望 JSch 自动获取默认 OpenSSH 密钥时：
\n Getting "com.jcraft.jsch.JSchException: Auth failed" \xe2\x80\x93 but "ssh" can log using public key authentication