Hi all, I am trying to setup rsync to create a mirror of a production server using -e ssh. In my scenario an anonymous rsync server won't work.
I can get the rsync to do what I want perfectly except that that ssh is requiring I enter either the password or passphrase depending on the iteration of the sshd_config file I am using. I need to initiate the rsync as root. Again this all works fine if I enter the passphrase or password for root. However I want to put this in as a crontab entry. I have tried the various options for protocol versions 1 and 2 with the same results. Below is a debug session from when I try to do a simple ssh to the host: debug1: sshd version OpenSSH_3.1p1 debug1: private host key: #0 type 0 RSA1 debug1: read PEM private key done: type RSA debug1: private host key: #1 type 1 RSA debug1: read PEM private key done: type DSA debug1: private host key: #2 type 2 DSA socket: Address family not supported by protocol debug1: Bind to port 22 on 0.0.0.0. Server listening on 0.0.0.0 port 22. Generating 768 bit RSA key. RSA key generation complete. debug1: Server will not fork when running in debugging mode. Connection from 67.92.243.41 port 40777 debug1: Client protocol version 2.0; client software version OpenSSH_3.1p1 debug1: match: OpenSSH_3.1p1 pat OpenSSH* Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-1.99-OpenSSH_3.1p1 debug1: Rhosts Authentication disabled, originating port 40777 not trusted. debug1: list_hostkey_types: ssh-rsa,ssh-dss debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: client->server aes128-cbc hmac-md5 none debug1: kex: server->client aes128-cbc hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST received debug1: SSH2_MSG_KEX_DH_GEX_GROUP sent debug1: dh_gen_key: priv key bits set: 133/256 debug1: bits set: 1574/3191 debug1: expecting SSH2_MSG_KEX_DH_GEX_INIT debug1: bits set: 1646/3191 debug1: SSH2_MSG_KEX_DH_GEX_REPLY sent debug1: kex_derive_keys debug1: newkeys: mode 1 debug1: SSH2_MSG_NEWKEYS sent debug1: waiting for SSH2_MSG_NEWKEYS debug1: newkeys: mode 0 debug1: SSH2_MSG_NEWKEYS received debug1: KEX done debug1: userauth-request for user root service ssh-connection method none debug1: attempt 0 failures 0 debug1: Starting up PAM with username "root" debug1: PAM setting rhost to "mail.loanprocessing.net" Failed none for root from 67.92.243.41 port 40777 ssh2 debug1: userauth-request for user root service ssh-connection method publickey debug1: attempt 1 failures 1 debug1: test whether pkalg/pkblob are acceptable debug1: temporarily_use_uid: 0/0 (e=0) debug1: trying public key file /root/.ssh/authorized_keys debug1: matching key found: file /root/.ssh/authorized_keys, line 2 Found matching RSA key: 41:1f:f7:62:f4:be:81:8a:92:b7:cb:b1:a5:11:1d:75 debug1: restore_uid Postponed publickey for root from 67.92.243.41 port 40777 ssh2 My questions are: How do I create a trusted port (see output above) and will that work with rsync? Why does PAM authentication fail above? Additional info: The client I am attaching with has several conanical names in named. Any help appreciated on this, Mike Mike McMullen CIO - Baton, Inc. 7637 Fair Oaks Blvd Suite #2 Carmichael, CA 95608 Tel: 1-866-515-4421 or 916-944-7790 ext. 2 Fax: 1-866-843-8795 or 916-944-8422 Email: [EMAIL PROTECTED] Web: www.loanprocessing.net "From chaos comes true genius..." -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
