Geek asks and answers

CentOS scp without password does not work

I tried to connect from one EC2 instance to another using ssh public keys and had a very difficult time.

Here is the scenario: I need to have box 2 scp file from box 1 in script. This script should be able to scp without a password, so I need to configure the public keys.

In field 2 I started ssh-keygen –t rsaand generated id_rsaand id_rsa.pub I copied id_rsa.pubin field 1 I moved id_rsa.pubto .ssh and started cat id_rsa.pug >> authorized_keys I changed the permissions for all .ssh directories to 700 on both boxes and the files themselves to 600. I changed the sshd_config settings in field 1 to:

RSAAuthentication yes
PubkeyAuthentication yes
AuthorizedKeysFile      .ssh/authorized_keys

And then reload ssh

/sbin/service sshd restart

When I try to execute scp or ssh in box1 from box1, I get an error:

Address 67.22.33.1 maps to ec2-67-22-33-1.compute-1.amazonaws.com, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!
tomcat@tomcat1.****.com password:

Any ideas?

scp to tomcat1, . :

debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug1: Connecting to tomcat1.****.com [67.22.33.15] port 22.
debug1: Connection established.
debug1: identity file /home/tomcat/.ssh/identity type -1
debug1: identity file /home/tomcat/.ssh/id_rsa type 1
debug1: identity file /home/tomcat/.ssh/id_dsa type -1
debug1: loaded 3 keys
debug1: Remote protocol version 2.0, remote software version OpenSSH_4.3
debug1: match: OpenSSH_4.3 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_4.3
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-cbc hmac-md5 none
debug1: kex: client->server aes128-cbc 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
The authenticity of host 'tomcat1.****.com (67.22.33.15)' can't be established.
RSA key fingerprint is 5a:3e:fe:be:b8:0e:05:63:bf:ab:c8:4f:e5:91:db:a0.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added 'tomcat1.****.com,67.22.33.15' (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: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey,password
debug1: Next authentication method: publickey
debug1: Trying private key: /home/tomcat/.ssh/identity
debug1: Offering public key: /home/tomcat/.ssh/id_rsa
debug1: Authentications that can continue: publickey,password
debug1: Trying private key: /home/tomcat/.ssh/id_dsa
debug1: Next authentication method: password
+3
7

AuthorizedKeysFile     %h/.ssh/authorized_keys

.

+1

-

restorecon -R -v -d /root/.ssh

RH, , PAM sshd authorized_hosts init script. , /var/log/audit/audit.log. , , !

https://bugzilla.redhat.com/show_bug.cgi?id=499343

, . VirtualBox ( vbox 64-), , ( 64- Vbox RedHat), .

- - , .

, , , sshd, , /usr/sbin/sshd root, . , .

, /etc/init.d/sshd. , ... script, /etc/init.d/sshd start, /usr/sbin/sshd.

, , - ??

+1

box1 IP ~/.ssh/known_hosts, . , ssh - " ".

, GSSAPIAuthentication no /etc/ssh/ssh_config.

0

, , ssh not login. - ssh root @node02 'restorecon -R -v/root/.ssh' SE http://blog.firedaemon.com/2011/07/27/passwordless-root-ssh-public-key-authentication-on-centos-6/

0

, ".." .ssh:

~/.ssh:

drwx ------ 2 build build 4096 4 14:35.

drwx ------ 6 build build 4096 4 14:34..

-rw ------- 1 build build 400 4 14:35 authorized_keys

!

. Damian

0

, . , sshd_config.

.ssh- .

chmod 700 ~/.ssh

next, /etc/ssh/sshd _config, StrictModes yes StrictModes no. , StrictModes no .

.

0

And one more thing I just found, I had to edit the .ssh / authorized_keys file and make the fully qualified host name. Otherwise, I could not use the full name in the scp / ssh command. Now fully qualified (for example, "host.company.com") and relative name ("host") work, given that both nodes are in the domain "company.com". ssh-keygen created a public key file with only the host name.

0
source

More articles:


All Articles