无法使用 pem 私钥进行 ssh（未找到 dlopen 图像）[关闭]

Posted 2023-03-04

【中文标题】无法使用 pem 私钥进行 ssh（未找到 dlopen 图像）[关闭]

【英文标题】：ssh with private pem key not possible (dlopen image not found) [closed]

【发布时间】：2014-08-15 04:17:51

【问题描述】：

从今天晚上开始，我无法连接到我的 AWS EC2 实例。 它不断告诉我以下内容：

dlopen private.pem failed: dlopen(private.pem, 2): no suitable image found.  Did find:    private.pem: file too short

这是我的 ssh 连接的输出：

'''ssh $SSHOPTS -I private.pem admin@54.213.238.233
OpenSSH_6.2p2, OSSLShim 0.9.8r 8 Dec 2011
debug1: Reading configuration data /Users/evertvancauwenberg/.ssh/config
debug1: Reading configuration data /etc/ssh_config
debug1: /etc/ssh_config line 20: Applying options for *
debug1: /etc/ssh_config line 53: Applying options for *
debug1: Connecting to 54.213.238.233 [54.213.238.233] port 22.
debug1: Connection established.enter code here
dlopen private.pem failed: dlopen(private.pem, 2): no suitable image found.  Did find:
    private.pem: file too short
debug1: identity file /Users/evertvancauwenberg/.ssh/id_rsa type 1
debug1: identity file /Users/evertvancauwenberg/.ssh/id_rsa-cert type -1
debug1: identity file /Users/evertvancauwenberg/.ssh/id_dsa type -1
debug1: identity file /Users/evertvancauwenberg/.ssh/id_dsa-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_6.2
debug1: Remote protocol version 2.0, remote software version OpenSSH_6.0p1 Debian-4
debug1: match: OpenSSH_6.0p1 Debian-4 pat OpenSSH*
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-ctr hmac-md5 none
debug1: kex: client->server aes128-ctr hmac-md5 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Server host key: RSA 6f:80:22:e6:cd:c0:84:c4:1c:11:a8:bb:ee:55:2e:75
The authenticity of host '54.213.238.233 (54.213.238.233)' can't be established.
RSA key fingerprint is 6f:80:22:e6:cd:c0:84:c4:1c:11:a8:bb:ee:55:2e:75.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '54.213.238.233' (RSA) to the list of known hosts.
debug1: ssh_rsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: Roaming not allowed by server
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey
debug1: Next authentication method: publickey
debug1: Offering RSA public key: /Users/evertvancauwenberg/.ssh/id_rsa
debug1: Authentications that can continue: publickey
debug1: Trying private key: /Users/evertvancauwenberg/.ssh/id_dsa
debug1: No more authentication methods to try.
Permission denied (publickey).

我正在使用 OSX 10.9.2 用 ssh -v

OpenSSH_6.2p2，OSSLShim 0.9.8r 2011 年 12 月 8 日

usage: ssh [-1246AaCfgKkMNnqsTtVvXxYy] [-b bind_address] [-c cipher_spec]
           [-D [bind_address:]port] [-e escape_char] [-F configfile]
           [-I pkcs11] [-i identity_file]
           [-L [bind_address:]port:host:hostport]
           [-l login_name] [-m mac_spec] [-O ctl_cmd] [-o option] [-p port]
           [-R [bind_address:]port:host:hostport] [-S ctl_path]
           [-W host:port] [-w local_tun[:remote_tun]]
           [user@]hostname [command]

【问题讨论】：

指定身份文件的选项是-i 而不是-I ...不是吗？

天哪：|我没有注意到！现在感觉很愚蠢...... THNX！

@Michael-sqlbot 也救了我，有点生疏。你应该提交正确的答案！

【参考方案1】：

您需要使用 -i（身份文件）选项而不是 -I（PKCS #11 共享库）来 ssh。

ssh -i private.pem user@ip

男人摘录：

 -I pkcs11
         Specify the PKCS#11 shared library ssh should use to communicate with a
         PKCS#11 token providing the user's private RSA key.

 -i identity_file
         Selects a file from which the identity (private key) for public key
         authentication is read.  The default is ~/.ssh/id_dsa, ~/.ssh/id_ecdsa,
         ~/.ssh/id_ed25519 and ~/.ssh/id_rsa.  Identity files may also be specified
         on a per-host basis in the configuration file.  It is possible to have
         multiple -i options (and multiple identities specified
         in configuration files).  If no certificates have been explicitly specified
         by the CertificateFile directive, ssh will also try to load certificate
         information from the filename obtained by appending -cert.pub to identity
         filenames.

【讨论】：

这么容易的错字，谢谢！

是的，一个非常容易的错字和一个非常混乱的错误信息。刚刚阅读了手册页，我“知道”这不是我的问题……除了它是（我一定是下意识地按下了 SHIFT 键）。也谢谢你救了我！