CentOS - May 2016 - google cloud compute with PEM file

On Tue, 17 May 2016 13:59:18 -0600
Dustin Kempter wrote:
>  Is there something  I missed?
ssh -v serveryouwanttoconnectto

That will tell you what the problem is.

If you don't understand the output, post it here.

-- 
MELVILLE THEATRE ~ Real D 3D Digital Cinema ~ www.melvilletheatre.com

On 5/17/16 2:12 PM, Frank Cox wrote:
> On Tue, 17 May 2016 13:59:18 -0600
> Dustin Kempter wrote:
>
>>   Is there something  I missed?
> ssh -v serveryouwanttoconnectto
>
> That will tell you what the problem is.
>
> If you don't understand the output, post it here.
>
Here is the command and output


[test1 at pgpool1 ~]$ ssh -v -i /home/test1/my-key.txt upload at 144.167.188.62
OpenSSH_5.3p1, OpenSSL 1.0.1e-fips 11 Feb 2013
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug1: Connecting to 104.197.158.61 [104.197.158.61] port 22.
debug1: Connection established.
debug1: identity file /home/test1/my-key.txt type 1
debug1: identity file /home/test1/my-key.txt-cert type -1
debug1: Remote protocol version 2.0, remote software version OpenSSH_5.3
debug1: match: OpenSSH_5.3 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_5.3
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: Host '104.197.158.61' is known and matches the RSA host key.
debug1: Found key in /home/test1/.ssh/known_hosts:1
debug1: ssh_rsa_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,gssapi-keyex,gssapi-with-mic
debug1: Next authentication method: gssapi-keyex
debug1: No valid Key exchange context
debug1: Next authentication method: gssapi-with-mic
debug1: Unspecified GSS failure.  Minor code may provide more information
Credentials cache file '/tmp/krb5cc_501' not found

debug1: Unspecified GSS failure.  Minor code may provide more information
Credentials cache file '/tmp/krb5cc_501' not found

debug1: Unspecified GSS failure.  Minor code may provide more information


debug1: Unspecified GSS failure.  Minor code may provide more information
Credentials cache file '/tmp/krb5cc_501' not found

debug1: Next authentication method: publickey
debug1: Offering public key: /home/test1/my-key.txt
debug1: Server accepts key: pkalg ssh-rsa blen 277
debug1: PEM_read_PrivateKey failed
debug1: read PEM private key done: type <unknown>
Enter passphrase for key '/home/test1/my-key.txt':
debug1: No more authentication methods to try.
Permission denied (publickey,gssapi-keyex,gssapi-with-mic).
[test1 at pgpool1 ~]$

On Tue, 17 May 2016 14:34:03 -0600
Dustin Kempter wrote:
> Enter passphrase for key '/home/test1/my-key.txt':
Since your private key is encrypted, have you entered the passphrase for the
private key when asked at this point in the login?

-- 
MELVILLE THEATRE ~ Real D 3D Digital Cinema ~ www.melvilletheatre.com

On Tue, 2016-05-17 at 14:34 -0600, Dustin Kempter wrote:
> Connecting to 104.197.158.61 [104.197.158.61] port 22.
(1)  I would change the port from 22 to something more difficult to
guess, perhaps 49026 (for example) and then block port 22 in the
firewall.

(2)  Allow to port 49026 (for example) traffic from your IP and block
traffic from all other IPs.


Do not forget there are people out there desperate to get into your
computer system, so make it more difficult for them.


-- 
Regards,

Paul.
England, EU.      England's place is in the European Union.