Ssh Config Editor Pro 1 11 5 Iso
Hyper-V has been included with Windows since Windows Server 2008 as well as Windows 8, 8.1, and 10 in the Pro versions. It can be enabled from the Control Panel at “Turn Windows features on. Download SSH Config Editor for macOS 10.15 or later and enjoy it on your Mac. Handy tool for manage your OpenSSH ssh client configuration file. You can add or edit identity files, port forwardings (with graphical preview) and any other ssh config option. When running just version 1: R1(config)#ip ssh ver 1. SSH Enabled - version 1.5. Authentication timeout: 120 secs; Authentication retries: 3. When running version 1 and 2 (default) R1(config)#no ip ssh ver. SSH Enabled - version 1.99. Authentication timeout: 120 secs; Authentication retries: 3. When running version 2: R1(config)#. The feature which is in our opinion the most useful may be the graphical SSH-browser: when you log to a remote server using SSH, a graphical SSH-browser pops up on in the left sidebar allowing you to drag and drop files directly from or to the remote server using your secure SSH connection and SFTP or SCP protocol. Home Forums General Technology Computer Zone PC Apllications SSH Config Editor Pro 1.11.5 macOS Welcome to Ramleague, Ramleague - the best site for pinoy chat, games chat and mobiles chat.
Ssh Config Editor Pro 1 11 5 Iso Bootable
Hi,
i find this .ssh/config file frustrating sometimes. I have spent cycles on this today, but i still dont understand why its doing what it is doing. So, i have the .ssh/config file as below and it was working just the way, i wanted.
Host ec2-*.amazonaws.com
HostName ec2-*.amazonaws.com
User root
IdentityFile ~/.ssh/123-eastkey.pem
# IdentitiesOnly yes
Host github.com
HostName github.com
PreferredAuthentications publickey
IdentityFile ~/.ssh/id_rsa_nopass
# IdentitiesOnly yes
#Host cgit-pro.cnn.com
# HostName cgit-pro.cnn.com
# User ctf_build
# IdentityFile ~/keys/github/ctf_build.rsa
Host *
StrictHostKeyChecking no
# IdentitiesOnly yes
The commented lines were added today for troubleshooting.
Then, i had to change the key in this file from '~/.ssh/123-eastkey.pem' to something else. I did that and saved the file. Then since than, i am going through all kind of issues while trying to connect to the servers. The verbose output shows that the right private key was never tried. Even with the 'IdentitiesOnly yes' set.
It only works now, if i put in the exact FQDN of the server for the Host & Hostname. How can i set this file, so that i dont need to specify the entire/exact hostnames. The man page, says i should be able to use something like '*.amazonaws.com'
Now, i have the below entry in .ssh/config file
Host *.amazonaws.com
HostName ec2*.compute-1.amazonaws.com
User root
IdentityFile ~/.ssh/123-eastkey.pem
# IdentitiesOnly yes
2.2.1:~ $ ssh root@ec2-52-7-226-0.compute-1.amazonaws.com
ssh: Could not resolve hostname ec2*.compute-1.amazonaws.com: Name or service not known
-- update:
Now i changed the file entry to like this, it stopped saying 'ssh: Could not resolve hostname.....'
Host awshost
HostName ec2*.compute-1.amazonaws.com
User root
IdentityFile ~/.ssh/123-devops-eastkey.pem
IdentitiesOnly yes
But its not using the right 'identityFile' as specified in the file.
See below the verbose output: (Its trying with some typical key names, this just redicules the idea of the config file)
2.2.1:~ $ ssh root@ec2-52-7-226-0.compute-1.amazonaws.com -v
OpenSSH_5.9p1 Debian-5ubuntu1.4, OpenSSL 1.0.1 14 Mar 2012
debug1: Reading configuration data /home/chef/.ssh/config
debug1: /home/chef/.ssh/config line 24: Applying options for *
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug1: Connecting to ec2-52-7-226-0.compute-1.amazonaws.com [52.7.226.0] port 22.
debug1: Connection established.
debug1: identity file /home/chef/.ssh/id_rsa type -1
debug1: identity file /home/chef/.ssh/id_rsa-cert type -1
debug1: identity file /home/chef/.ssh/id_dsa type -1
debug1: identity file /home/chef/.ssh/id_dsa-cert type -1
debug1: identity file /home/chef/.ssh/id_ecdsa type -1
debug1: identity file /home/chef/.ssh/id_ecdsa-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.9p1 Debian-5ubuntu1.4
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 87:6e:ab:e3:11:94:22:01:ac:6b:44:77:ba:e9:db:18
debug1: Host 'ec2-52-7-226-0.compute-1.amazonaws.com' is known and matches the RSA host key.
debug1: Found key in /home/chef/.ssh/known_hosts:3
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,gssapi-keyex,gssapi-with-mic,password
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_1000' not found
debug1: Unspecified GSS failure. Minor code may provide more information
Credentials cache file '/tmp/krb5cc_1000' 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_1000' not found
debug1: Next authentication method: publickey
debug1: Offering RSA public key: ubuntu12-vm
debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic,password
debug1: Trying private key: /home/chef/.ssh/id_rsa
debug1: Trying private key: /home/chef/.ssh/id_dsa
debug1: Trying private key: /home/chef/.ssh/id_ecdsa
debug1: Next authentication method: password
root@ec2-52-7-226-0.compute-1.amazonaws.com's password:
Update:
This is really disgusting ... So i changed the private key name from 'whatever.pem' to 'id_rsa' .. And things started working again.
Is this the way how it should work??
i find this .ssh/config file frustrating sometimes. I have spent cycles on this today, but i still dont understand why its doing what it is doing. So, i have the .ssh/config file as below and it was working just the way, i wanted.
Host ec2-*.amazonaws.com
HostName ec2-*.amazonaws.com
User root
IdentityFile ~/.ssh/123-eastkey.pem
# IdentitiesOnly yes
Host github.com
HostName github.com
PreferredAuthentications publickey
IdentityFile ~/.ssh/id_rsa_nopass
# IdentitiesOnly yes
#Host cgit-pro.cnn.com
# HostName cgit-pro.cnn.com
# User ctf_build
# IdentityFile ~/keys/github/ctf_build.rsa
Host *
StrictHostKeyChecking no
# IdentitiesOnly yes
The commented lines were added today for troubleshooting.
Then, i had to change the key in this file from '~/.ssh/123-eastkey.pem' to something else. I did that and saved the file. Then since than, i am going through all kind of issues while trying to connect to the servers. The verbose output shows that the right private key was never tried. Even with the 'IdentitiesOnly yes' set.
It only works now, if i put in the exact FQDN of the server for the Host & Hostname. How can i set this file, so that i dont need to specify the entire/exact hostnames. The man page, says i should be able to use something like '*.amazonaws.com'
Now, i have the below entry in .ssh/config file
Host *.amazonaws.com
HostName ec2*.compute-1.amazonaws.com
User root
IdentityFile ~/.ssh/123-eastkey.pem
# IdentitiesOnly yes
2.2.1:~ $ ssh root@ec2-52-7-226-0.compute-1.amazonaws.com
ssh: Could not resolve hostname ec2*.compute-1.amazonaws.com: Name or service not known
-- update:
Now i changed the file entry to like this, it stopped saying 'ssh: Could not resolve hostname.....'
Host awshost
HostName ec2*.compute-1.amazonaws.com
User root
IdentityFile ~/.ssh/123-devops-eastkey.pem
IdentitiesOnly yes
But its not using the right 'identityFile' as specified in the file.
See below the verbose output: (Its trying with some typical key names, this just redicules the idea of the config file)
2.2.1:~ $ ssh root@ec2-52-7-226-0.compute-1.amazonaws.com -v
OpenSSH_5.9p1 Debian-5ubuntu1.4, OpenSSL 1.0.1 14 Mar 2012
debug1: Reading configuration data /home/chef/.ssh/config
debug1: /home/chef/.ssh/config line 24: Applying options for *
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug1: Connecting to ec2-52-7-226-0.compute-1.amazonaws.com [52.7.226.0] port 22.
debug1: Connection established.
debug1: identity file /home/chef/.ssh/id_rsa type -1
debug1: identity file /home/chef/.ssh/id_rsa-cert type -1
debug1: identity file /home/chef/.ssh/id_dsa type -1
debug1: identity file /home/chef/.ssh/id_dsa-cert type -1
debug1: identity file /home/chef/.ssh/id_ecdsa type -1
debug1: identity file /home/chef/.ssh/id_ecdsa-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.9p1 Debian-5ubuntu1.4
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 87:6e:ab:e3:11:94:22:01:ac:6b:44:77:ba:e9:db:18
debug1: Host 'ec2-52-7-226-0.compute-1.amazonaws.com' is known and matches the RSA host key.
debug1: Found key in /home/chef/.ssh/known_hosts:3
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,gssapi-keyex,gssapi-with-mic,password
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_1000' not found
debug1: Unspecified GSS failure. Minor code may provide more information
Credentials cache file '/tmp/krb5cc_1000' 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_1000' not found
debug1: Next authentication method: publickey
debug1: Offering RSA public key: ubuntu12-vm
debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic,password
debug1: Trying private key: /home/chef/.ssh/id_rsa
debug1: Trying private key: /home/chef/.ssh/id_dsa
debug1: Trying private key: /home/chef/.ssh/id_ecdsa
debug1: Next authentication method: password
root@ec2-52-7-226-0.compute-1.amazonaws.com's password:
Update:
This is really disgusting ... So i changed the private key name from 'whatever.pem' to 'id_rsa' .. And things started working again.
Is this the way how it should work??
Ssh Config Example
Hi,
i find this .ssh/config file frustrating sometimes. I have spent cycles on this today, but i still dont understand why its doing what it is doing. So, i have the .ssh/config file as below and it was working just the way, i wanted.
Host ec2-*.amazonaws.com
HostName ec2-*.amazonaws.com
User root
IdentityFile ~/.ssh/123-eastkey.pem
# IdentitiesOnly yes
Host github.com
HostName github.com
PreferredAuthentications publickey
IdentityFile ~/.ssh/id_rsa_nopass
# IdentitiesOnly yes
#Host cgit-pro.cnn.com
# HostName cgit-pro.cnn.com
# User ctf_build
# IdentityFile ~/keys/github/ctf_build.rsa
Host *
StrictHostKeyChecking no
# IdentitiesOnly yes
The commented lines were added today for troubleshooting.
Then, i had to change the key in this file from '~/.ssh/123-eastkey.pem' to something else. I did that and saved the file. Then since than, i am going through all kind of issues while trying to connect to the servers. The verbose output shows that the right private key was never tried. Even with the 'IdentitiesOnly yes' set.
It only works now, if i put in the exact FQDN of the server for the Host & Hostname. How can i set this file, so that i dont need to specify the entire/exact hostnames. The man page, says i should be able to use something like '*.amazonaws.com'
Now, i have the below entry in .ssh/config file
Host *.amazonaws.com
HostName ec2*.compute-1.amazonaws.com
User root
IdentityFile ~/.ssh/123-eastkey.pem
# IdentitiesOnly yes
2.2.1:~ $ ssh root@ec2-52-7-226-0.compute-1.amazonaws.com
ssh: Could not resolve hostname ec2*.compute-1.amazonaws.com: Name or service not known
-- update:
Now i changed the file entry to like this, it stopped saying 'ssh: Could not resolve hostname.....'
Host awshost
HostName ec2*.compute-1.amazonaws.com
User root
IdentityFile ~/.ssh/123-devops-eastkey.pem
IdentitiesOnly yes
But its not using the right 'identityFile' as specified in the file.
See below the verbose output: (Its trying with some typical key names, this just redicules the idea of the config file)
2.2.1:~ $ ssh root@ec2-52-7-226-0.compute-1.amazonaws.com -v
OpenSSH_5.9p1 Debian-5ubuntu1.4, OpenSSL 1.0.1 14 Mar 2012
debug1: Reading configuration data /home/chef/.ssh/config
debug1: /home/chef/.ssh/config line 24: Applying options for *
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug1: Connecting to ec2-52-7-226-0.compute-1.amazonaws.com [52.7.226.0] port 22.
debug1: Connection established.
debug1: identity file /home/chef/.ssh/id_rsa type -1
debug1: identity file /home/chef/.ssh/id_rsa-cert type -1
debug1: identity file /home/chef/.ssh/id_dsa type -1
debug1: identity file /home/chef/.ssh/id_dsa-cert type -1
debug1: identity file /home/chef/.ssh/id_ecdsa type -1
debug1: identity file /home/chef/.ssh/id_ecdsa-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.9p1 Debian-5ubuntu1.4
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 87:6e:ab:e3:11:94:22:01:ac:6b:44:77:ba:e9:db:18
debug1: Host 'ec2-52-7-226-0.compute-1.amazonaws.com' is known and matches the RSA host key.
debug1: Found key in /home/chef/.ssh/known_hosts:3
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,gssapi-keyex,gssapi-with-mic,password
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_1000' not found
debug1: Unspecified GSS failure. Minor code may provide more information
Credentials cache file '/tmp/krb5cc_1000' 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_1000' not found
debug1: Next authentication method: publickey
debug1: Offering RSA public key: ubuntu12-vm
debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic,password
debug1: Trying private key: /home/chef/.ssh/id_rsa
debug1: Trying private key: /home/chef/.ssh/id_dsa
debug1: Trying private key: /home/chef/.ssh/id_ecdsa
debug1: Next authentication method: password
root@ec2-52-7-226-0.compute-1.amazonaws.com's password:
Update:
This is really disgusting ... So i changed the private key name from 'whatever.pem' to 'id_rsa' .. And things started working again.
Is this the way how it should work??
i find this .ssh/config file frustrating sometimes. I have spent cycles on this today, but i still dont understand why its doing what it is doing. So, i have the .ssh/config file as below and it was working just the way, i wanted.
Host ec2-*.amazonaws.com
HostName ec2-*.amazonaws.com
User root
IdentityFile ~/.ssh/123-eastkey.pem
# IdentitiesOnly yes
Host github.com
HostName github.com
PreferredAuthentications publickey
IdentityFile ~/.ssh/id_rsa_nopass
# IdentitiesOnly yes
#Host cgit-pro.cnn.com
# HostName cgit-pro.cnn.com
# User ctf_build
# IdentityFile ~/keys/github/ctf_build.rsa
Host *
StrictHostKeyChecking no
# IdentitiesOnly yes
The commented lines were added today for troubleshooting.
Then, i had to change the key in this file from '~/.ssh/123-eastkey.pem' to something else. I did that and saved the file. Then since than, i am going through all kind of issues while trying to connect to the servers. The verbose output shows that the right private key was never tried. Even with the 'IdentitiesOnly yes' set.
It only works now, if i put in the exact FQDN of the server for the Host & Hostname. How can i set this file, so that i dont need to specify the entire/exact hostnames. The man page, says i should be able to use something like '*.amazonaws.com'
Now, i have the below entry in .ssh/config file
Host *.amazonaws.com
HostName ec2*.compute-1.amazonaws.com
User root
IdentityFile ~/.ssh/123-eastkey.pem
# IdentitiesOnly yes
2.2.1:~ $ ssh root@ec2-52-7-226-0.compute-1.amazonaws.com
ssh: Could not resolve hostname ec2*.compute-1.amazonaws.com: Name or service not known
-- update:
Now i changed the file entry to like this, it stopped saying 'ssh: Could not resolve hostname.....'
Host awshost
HostName ec2*.compute-1.amazonaws.com
User root
IdentityFile ~/.ssh/123-devops-eastkey.pem
IdentitiesOnly yes
But its not using the right 'identityFile' as specified in the file.
See below the verbose output: (Its trying with some typical key names, this just redicules the idea of the config file)
2.2.1:~ $ ssh root@ec2-52-7-226-0.compute-1.amazonaws.com -v
OpenSSH_5.9p1 Debian-5ubuntu1.4, OpenSSL 1.0.1 14 Mar 2012
debug1: Reading configuration data /home/chef/.ssh/config
debug1: /home/chef/.ssh/config line 24: Applying options for *
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug1: Connecting to ec2-52-7-226-0.compute-1.amazonaws.com [52.7.226.0] port 22.
debug1: Connection established.
debug1: identity file /home/chef/.ssh/id_rsa type -1
debug1: identity file /home/chef/.ssh/id_rsa-cert type -1
debug1: identity file /home/chef/.ssh/id_dsa type -1
debug1: identity file /home/chef/.ssh/id_dsa-cert type -1
debug1: identity file /home/chef/.ssh/id_ecdsa type -1
debug1: identity file /home/chef/.ssh/id_ecdsa-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.9p1 Debian-5ubuntu1.4
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 87:6e:ab:e3:11:94:22:01:ac:6b:44:77:ba:e9:db:18
debug1: Host 'ec2-52-7-226-0.compute-1.amazonaws.com' is known and matches the RSA host key.
debug1: Found key in /home/chef/.ssh/known_hosts:3
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,gssapi-keyex,gssapi-with-mic,password
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_1000' not found
debug1: Unspecified GSS failure. Minor code may provide more information
Credentials cache file '/tmp/krb5cc_1000' 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_1000' not found
debug1: Next authentication method: publickey
debug1: Offering RSA public key: ubuntu12-vm
debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic,password
debug1: Trying private key: /home/chef/.ssh/id_rsa
debug1: Trying private key: /home/chef/.ssh/id_dsa
debug1: Trying private key: /home/chef/.ssh/id_ecdsa
debug1: Next authentication method: password
root@ec2-52-7-226-0.compute-1.amazonaws.com's password:
Update:
This is really disgusting ... So i changed the private key name from 'whatever.pem' to 'id_rsa' .. And things started working again.
Is this the way how it should work??