Amazon web services 通过ssh连接而不访问主文件夹
我已经在AmazonEC2上安装了一个tomcat，我正试图在/home/ec2user/folder的文件夹中编写这个应用程序。 但是我没有得到，因为tomcat用户拥有该文件夹的权限 我试图更改tomcat用户的所有者，但都没有成功。 我想可能是文件夹/home/ec2 user/出了问题，然后更改到该文件夹的权限。。。但没有起作用 搜索Internet时，我找到了命令Amazon web services 通过ssh连接而不访问主文件夹,amazon-web-services,ssh,amazon-ec2,Amazon Web Services,Ssh,Amazon Ec2,我已经在AmazonEC2上安装了一个tomcat，我正试图在/home/ec2user/folder的文件夹中编写这个应用程序。 但是我没有得到，因为tomcat用户拥有该文件夹的权限 我试图更改tomcat用户的所有者，但都没有成功。 我想可能是文件夹/home/ec2 user/出了问题，然后更改到该文件夹的权限。。。但没有起作用 搜索Internet时，我找到了命令setEnforce0，但它不起作用 然后我关闭会话，当我再次尝试登录时收到以下消息 ssh -i "Amazon-Tomc
setEnforce0ssh -i "Amazon-Tomcat.pem" ec2-user@ec2-52-39-23-66.us-west-2.compute.amazonaws.com
Permission denied (publickey).
ssh -i "Amazon-Tomcat.pem" ec2-user@ec2-52-39-23-66.us-west-2.compute.amazonaws.com -v
OpenSSH_6.6.1, OpenSSL 1.0.1f 6 Jan 2014
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug1: Connecting to ec2-52-39-23-66.us-west-2.compute.amazonaws.com [52.39.23.66] port 22.
debug1: Connection established.
debug1: identity file Amazon-Tomcat.pem type -1
debug1: identity file Amazon-Tomcat.pem-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_6.6.1p1 Ubuntu-2ubuntu2.6
debug1: Remote protocol version 2.0, remote software version OpenSSH_6.6.1
debug1: match: OpenSSH_6.6.1 pat OpenSSH_6.6.1* compat 0x04000000
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-ctr hmac-md5-etm@openssh.com none
debug1: kex: client->server aes128-ctr hmac-md5-etm@openssh.com none
debug1: sending SSH2_MSG_KEX_ECDH_INIT
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server host key: ECDSA 21:76:3c:72:dd:68:14:c5:83:a6:09:9a:80:26:74:bc
debug1: Host 'ec2-52-39-23-66.us-west-2.compute.amazonaws.com' is known and matches the ECDSA host key.
debug1: Found key in /home/rodrigo/.ssh/known_hosts:7
debug1: ssh_ecdsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
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: OpenShift-Key
debug1: Authentications that can continue: publickey
debug1: Trying private key: Amazon-Tomcat.pem
debug1: key_parse_private2: missing begin marker
debug1: read PEM private key done: type RSA
debug1: Authentications that can continue: publickey
debug1: No more authentication methods to try.
Permission denied (publickey).
ssh -i "Amazon-Tomcat.pem" root@ec2-52-39-23-66.us-west-2.compute.amazonaws.com
Please login as the user "ec2-user" rather than the user "root".
Connection to ec2-52-39-23-66.us-west-2.compute.amazonaws.com closed.
ssh -i "Amazon-Tomcat.pem" ec2-user@ec2-52-39-23-66.us-west-2.compute.amazonaws.com
Permission denied (publickey).
ssh -i "Amazon-Tomcat.pem" ec2-user@ec2-52-39-23-66.us-west-2.compute.amazonaws.com -v
OpenSSH_6.6.1, OpenSSL 1.0.1f 6 Jan 2014
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug1: Connecting to ec2-52-39-23-66.us-west-2.compute.amazonaws.com [52.39.23.66] port 22.
debug1: Connection established.
debug1: identity file Amazon-Tomcat.pem type -1
debug1: identity file Amazon-Tomcat.pem-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_6.6.1p1 Ubuntu-2ubuntu2.6
debug1: Remote protocol version 2.0, remote software version OpenSSH_6.6.1
debug1: match: OpenSSH_6.6.1 pat OpenSSH_6.6.1* compat 0x04000000
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-ctr hmac-md5-etm@openssh.com none
debug1: kex: client->server aes128-ctr hmac-md5-etm@openssh.com none
debug1: sending SSH2_MSG_KEX_ECDH_INIT
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server host key: ECDSA 21:76:3c:72:dd:68:14:c5:83:a6:09:9a:80:26:74:bc
debug1: Host 'ec2-52-39-23-66.us-west-2.compute.amazonaws.com' is known and matches the ECDSA host key.
debug1: Found key in /home/rodrigo/.ssh/known_hosts:7
debug1: ssh_ecdsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
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: OpenShift-Key
debug1: Authentications that can continue: publickey
debug1: Trying private key: Amazon-Tomcat.pem
debug1: key_parse_private2: missing begin marker
debug1: read PEM private key done: type RSA
debug1: Authentications that can continue: publickey
debug1: No more authentication methods to try.
Permission denied (publickey).
非常感谢您提供的任何建议，请原谅我的愚蠢您错误地将.ssh密钥公钥的权限设置得过于宽松，这意味着ssh登录过程拒绝工作 若要解决此问题，请参阅此问题的得分最高的答案 基本上，您必须将磁盘从现在已损坏的ec2装载到新的ec2上并修复它 要解决原始问题（tomcat写入文件夹），请为/home/ec2用户主文件夹顶层提供“其他x”访问权限
chmod o+x /home/ec2-user
下次在您注销之前，测试ssh仍在工作 您错误地将.ssh密钥公钥的权限设置得过于宽松，这意味着ssh登录进程拒绝工作 若要解决此问题，请参阅此问题的得分最高的答案 基本上，您必须将磁盘从现在已损坏的ec2装载到新的ec2上并修复它 要解决原始问题（tomcat写入文件夹），请为/home/ec2用户主文件夹顶层提供“其他x”访问权限
chmod o+x /home/ec2-user
下次在您注销之前，测试ssh仍在工作 如果您使用的是Mac或linux/unix风格的机器，请再次运行ssh命令，然后tail-f/var/log/auth.log。最后几行将给出准确的错误消息。尝试将密钥对文件的权限更改为600（运行chmod 600 Amazon Tomcat.pem），然后再次尝试ssh。如果您使用的是Mac或linux/unix风格的计算机，请再次运行ssh命令，然后使用-f/var/log/auth.log。最后几行将给出准确的错误消息。尝试将密钥对文件的权限更改为600（运行chmod 600 Amazon Tomcat.pem），然后重试ssh。我假设
Amazon Tomcat.pemAmazon Tomcat.pem-cert.pubsshamazontomcat.pemAmazon Tomcat.pem-cert.pubssh