macos - 不能使用带有私用Pem key 的ssh(找不到dlopen镜像)

Question

Closed. This question does not meet Stack Overflow guidelines。它当前不接受答案。












想改善这个问题吗？更新问题，以便将其作为 on-topic用于堆栈溢出。

3年前关闭。



Improve this question




从今天晚上开始，我无法连接到我的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(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.

关于macos - 不能使用带有私用Pem key 的ssh(找不到dlopen镜像)，我们在Stack Overflow上找到一个类似的问题： https://stackoverflow.com/questions/24394483/

上一篇：angularjs - Angular UI Grid:如何创建用于列过滤的预填充下拉菜单

下一篇：当检索到的电子邮件与现有用户的电子邮件匹配时，django allauth facebook 重定向到注册？

相关文章：

macos - 如何对 Swift 结构使用 Cocoa 绑定(bind)

hadoop - 如何永久更改 sshd_config 文件？

networking - EC2-微型实例-网络响应/延迟/延迟非常慢

r - 在 AWS 上使用 Rserve 在 Node.js 和 R 之间进行跨平台通信时出错。错误:connect ETIMEDOUT

string - 验证 NSTextField 中的字符串是否为有效的 IP 地址或域名

macos - 如何直接在上下文菜单而不是服务子菜单中添加 mac OS 服务项？

xcode - 作为根进程调试的测试目标

linux - AWS Linux 实例上的权限被拒绝(公钥)

svn - svn checkout 时为 "Network connection closed unexpectedly"

node.js - 如何在 amazon ec2 中同时运行 Node 和 apache？

Answer 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.