osx - SSH Error: Permission denied (publickey,gssapi-with-mic) -


When trying to connect to EC2 on SSH, I get the following error: 

  joshua-Scotts-macbook-pro: .ec2 joshuascott $ ssh -v I OFMoodle root @ ec2-xxx-xxx -xxxx.compute-1.amazonaws.com OpenSSH_5.2p1 OpenSSL 0.9.8l November 5, 2009 debug1: Reading configuration data from / etc / ssh_config debug1: ec2-xxx-xxx-xxx-xx.com-pipe1.amazonaws.com Connecting [xxx.xxx.xxx.xxx] Port 22. debug1: The connection established. Debug1: Identity file OFMoodle Type-1 debug1: Remote Protocol Version 2.0, Remote Software Version OpenSSH_4.7 debug1: Match: OpenSSH_4.7 Pat OpenSSH_4 * debug1: Enabling Compatibility Mode for Protbug 2.0 Debug1: Local Version String SSH -2.0-OpenSSH_5. 2Dbug1: SSH2_MSG_KEXINIT Transmitted Debug 1: SSH2_MSG_KEXINIT Received Debug 1: KX: Server-> Client AES 128-CTR HMAC-MD5 No Debug 1: KX: Client-> Server AES 128-CTR HMCAC-MD5 no debug1: SSH2_MSG_KEX_DH_GEX_REQUEST (1024 <1024> 8192) sent debug1: Expected SSH2_MSG_KEX_DH_GEX_GROUP debug1: Expected SSH2_MSG_KEX_DH_GEX_REPLY debug1: SSH2_MSG_KEX_DH_GEX_INIT debug1 sent host 'ec2-xxx-xxx-xxx. Compute-1.amazonaws.com 'and matches the RSA host key. Debug 1: Used Key / User / Jojukat /.ssh/known_hosts:3 debug1: ssh_rsa_verify: Signature Correct Debug 1: SSH2_MSG_NEWKEYS Sent Debug 1: Expected SSH2_MSG_NEWKEYS Debug 1: SSH2_MSG_NEWKEYS Received Debug 1: SSH2_MSG_SERVICE_REQUEST sent debug 1: SSH2_MSG_SERVICE_ACCEPT received debug 1: Certification that can be continued: publickey, debug1 with GSSAPI-Mike: Next authentication method: publickey debug1: Prasad public key: PK-xxxxxxxxxxxxxxxxxxxxxxxxx.pem debug1: can continue authentication: publickey, GSSAPI-Mike Debug1: private keys The key is trying: OFMoodle debug1: read PEM private key: type RSA debug 1: authentication that can continue: publishing, with GSAPI-Mike debug 1: There are no more authentication methods to try Permission denied (Publisher, GSAPI-K-Mike)

I am completely in a disadvantage. I have many other examples which I can connect to any problem.

First I will make sure that the user is actually root and not < Em> ubuntu or EC2 user .

Otherwise, it may be that the permissions are .ssh / and .ssh / authorized_keys borked .


Comments

Post a Comment