SearchFAQMemberlist Log in
Reply to topic Page 1 of 1
problems with unattended backup
Author Message
Post problems with unattended backup 
Hello all!

I'm using rdiff-backup, and all runs ok, but I cannot do unattended
backup. I've read the doc at
http://www.arctic.org/~dean/rdiff-backup/unattended.html (excellent doc,
btw), without luck. Here is the output of the ssh -C command:

OpenSSH_3.4p1 Debian 1:3.4p1-1.woody.3, SSH protocols 1.5/2.0, OpenSSL
0x0090603f
debug1: Reading configuration data /root/.ssh/config
debug1: Applying options for powerfull
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Rhosts Authentication disabled, originating port will not be
trusted.
debug1: ssh_connect: needpriv 0
debug1: Connecting to powerfull [192.168.1.70] port 22.
debug1: Connection established.
debug3: Not a RSA1 key file /root/.ssh/id_rsa_backup.
debug2: key_type_from_name: unknown key type '-----BEGIN'
debug3: key_read: no key found
debug3: key_read: no space
debug3: key_read: no space
debug3: key_read: no space
debug3: key_read: no space
debug3: key_read: no space
debug3: key_read: no space
debug3: key_read: no space
debug3: key_read: no space
debug3: key_read: no space
debug3: key_read: no space
debug3: key_read: no space
debug3: key_read: no space
debug3: key_read: no space
debug2: key_type_from_name: unknown key type '-----END'
debug3: key_read: no key found
debug1: identity file /root/.ssh/id_rsa_backup type 1
debug1: Remote protocol version 1.99, remote software version 2.4.0 SSH
Secure Shell (non-commercial)
debug1: match: 2.4.0 SSH Secure Shell (non-commercial) pat 2.*
Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_3.4p1 Debian 1:3.4p1-1.woody.3
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug2: kex_parse_kexinit:
diffie-hellman-group-exchange-sha1,diffie-hellman-group1-sha1
debug2: kex_parse_kexinit: ssh-rsa,ssh-dss
debug2: kex_parse_kexinit:
aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour,aes192-cbc,aes256-cbc,rijndael-cbc < at > l
ysator.liu.se
debug2: kex_parse_kexinit:
aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour,aes192-cbc,aes256-cbc,rijndael-cbc < at > l
debug2: kex_parse_kexinit:
hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ripemd160 < at > openssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit:
hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ripemd160 < at > openssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: zlib
debug2: kex_parse_kexinit: zlib
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit: first_kex_follows 0
debug2: kex_parse_kexinit: reserved 0
debug2: kex_parse_kexinit: diffie-hellman-group1-sha1
debug2: kex_parse_kexinit: ssh-dss
debug2: kex_parse_kexinit:
3des-cbc,blowfish-cbc,twofish-cbc,arcfour,cast128-cbc,3des-ecb,3des-cfb,3des-ofb,cast128-
ecb,cast128-cfb,cast128-ofb,cast128-12-ecb,cast128-12-cbc,cast128-12-cfb,cast128-12-ofb,blowfish-ecb,blowfish-cfb,bl
owfish-ofb,des-ecb,des-cbc,des-cfb,des-ofb,twofish-ecb,twofish-cfb,twofish-ofb
debug2: kex_parse_kexinit:
3des-cbc,blowfish-cbc,twofish-cbc,arcfour,cast128-cbc,3des-ecb,3des-cfb,3des-ofb,cast128-
ecb,cast128-cfb,cast128-ofb,cast128-12-ecb,cast128-12-cbc,cast128-12-cfb,cast128-12-ofb,blowfish-ecb,blowfish-cfb,bl
owfish-ofb,des-ecb,des-cbc,des-cfb,des-ofb,twofish-ecb,twofish-cfb,twofish-ofb
debug2: kex_parse_kexinit:
hmac-sha1,hmac-sha1-96,hmac-md5,hmac-md5-96,hmac-ripemd160,hmac-ripemd160-96,sha1-8,sha1,
md5-8,md5,ripemd160-8,ripemd160
debug2: kex_parse_kexinit:
hmac-sha1,hmac-sha1-96,hmac-md5,hmac-md5-96,hmac-ripemd160,hmac-ripemd160-96,sha1-8,sha1,
md5-8,md5,ripemd160-8,ripemd160
debug2: kex_parse_kexinit: none,zlib
debug2: kex_parse_kexinit: none,zlib
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit: first_kex_follows 0
debug2: kex_parse_kexinit: reserved 0
debug2: mac_init: found hmac-md5
debug1: kex: server->client 3des-cbc hmac-md5 zlib
debug2: mac_init: found hmac-md5
debug1: kex: client->server 3des-cbc hmac-md5 zlib
debug1: dh_gen_key: priv key bits set: 203/384
debug1: bits set: 516/1024
debug1: sending SSH2_MSG_KEXDH_INIT
debug1: expecting SSH2_MSG_KEXDH_REPLY
debug3: check_host_in_hostfile: filename /root/.ssh/known_hosts
debug3: check_host_in_hostfile: match line 1
debug3: check_host_in_hostfile: filename /root/.ssh/known_hosts
debug3: check_host_in_hostfile: match line 1
debug1: Host 'powerfull' is known and matches the DSA host key.
debug1: Found key in /root/.ssh/known_hosts:1
debug1: bits set: 509/1024
debug1: ssh_dss_verify: signature correct
debug1: kex_derive_keys
debug1: newkeys: mode 1
debug1: Enabling compression at level 6.
debug1: SSH2_MSG_NEWKEYS sent
debug1: waiting for SSH2_MSG_NEWKEYS
debug1: newkeys: mode 0
debug1: SSH2_MSG_NEWKEYS received
debug1: done: ssh_kex2.
debug1: send SSH2_MSG_SERVICE_REQUEST
debug1: service_accept: ssh-userauth
debug1: got SSH2_MSG_SERVICE_ACCEPT
debug1: authentications that can continue: publickey,password
debug3: start over, passed a different list publickey,password
debug3: preferred publickey,keyboard-interactive,password
debug3: authmethod_lookup publickey
debug3: remaining preferred: keyboard-interactive,password
debug3: authmethod_is_enabled publickey
debug1: next auth method to try is publickey
debug1: try pubkey: /root/.ssh/id_rsa_backup
debug3: send_pubkey_test
debug2: we sent a publickey packet, wait for reply
debug1: authentications that can continue: publickey,password
debug2: we did not send a packet, disable method <<<<<< PROBLEM ???
debug3: authmethod_lookup password
debug3: remaining preferred: ,password
debug3: authmethod_is_enabled password
debug1: next auth method to try is password
debug3: packet_send2: adding 24 (len 30 padlen 10 extra_pad 64)
debug2: we sent a password packet, wait for reply
debug1: authentications that can continue: publickey,password



Thanks in advance,
Carlos.

Post problems with unattended backup 
On Wed, 07 Jul 2004 10:35:08 +0200
Carlos Costa Portela <ccosta < at > smartec.es> wrote:

debug3: Not a RSA1 key file /root/.ssh/id_rsa_backup.
debug2: key_type_from_name: unknown key type '-----BEGIN'


No, THAT ^^^ is the problem.

Post problems with unattended backup 
Mmmm... but this id_rsa_backup is the generated by the "ssh-keygen -t
rsa" command.

Why is ssh looking for a rsa1 key file, instead of rsa one?

TIA,
Carlos.

debug3: Not a RSA1 key file /root/.ssh/id_rsa_backup.
debug2: key_type_from_name: unknown key type '-----BEGIN'



Post problems with unattended backup 
On Wed, 07 Jul 2004 11:58:28 +0200
Carlos Costa Portela <ccosta < at > smartec.es> wrote:

Why is ssh looking for a rsa1 key file, instead of rsa one?

My advice, fwiw, would be to get passwordless logins working before you
introduce rdiff-backup into the equation.

Keith

--
----------------------------------------------------------------------
Small business computer support: http://www.tiger-computing.co.uk
Linux consultancy: http://www.TheLinuxConsultancy.co.uk
----------------------------------------------------------------------

Post problems with unattended backup 
Keith Edmunds wrote:

On Wed, 07 Jul 2004 11:58:28 +0200
Carlos Costa Portela <ccosta < at > smartec.es> wrote:



Why is ssh looking for a rsa1 key file, instead of rsa one?



My advice, fwiw, would be to get passwordless logins working before you
introduce rdiff-backup into the equation.



I agree. Actually, my problem is get the passwordless login using ssh,
but the system looks for a rsa1 key file... that does not exist.

Thank you very much!
Carlos.

Post problems with unattended backup 
On Wed, 07 Jul 2004 12:31:17 +0200
Carlos Costa Portela <ccosta < at > smartec.es> wrote:

I agree. Actually, my problem is get the passwordless login using ssh,
but the system looks for a rsa1 key file... that does not exist.

Try putting "Protocol 2" in your system's sshd_config

Keith

--
----------------------------------------------------------------------
Small business computer support: http://www.tiger-computing.co.uk
Linux consultancy: http://www.TheLinuxConsultancy.co.uk
----------------------------------------------------------------------

Post problems with unattended backup 
On Wed, 7 Jul 2004, Carlos Costa Portela wrote:

debug3: Not a RSA1 key file /root/.ssh/id_rsa_backup.
debug2: key_type_from_name: unknown key type '-----BEGIN'
debug3: key_read: no key found
debug3: key_read: no space
debug3: key_read: no space
debug3: key_read: no space
debug3: key_read: no space
debug3: key_read: no space
debug3: key_read: no space
debug3: key_read: no space
debug3: key_read: no space
debug3: key_read: no space
debug3: key_read: no space
debug3: key_read: no space
debug3: key_read: no space
debug3: key_read: no space
debug2: key_type_from_name: unknown key type '-----END'
debug3: key_read: no key found

you shouldn't have -----BEGIN, ------END in your private key file...
that's all very suspicious. i'd take a look at the id_rsa_backup file and
see if it's been trashed somehow. it should be a binary file (the .pub
file is text)

-dean

Post problems with unattended backup 
On Wed, 7 Jul 2004, dean gaudet wrote:

On Wed, 7 Jul 2004, Carlos Costa Portela wrote:

debug3: Not a RSA1 key file /root/.ssh/id_rsa_backup.
debug2: key_type_from_name: unknown key type '-----BEGIN'
debug3: key_read: no key found
debug3: key_read: no space
debug3: key_read: no space
debug3: key_read: no space
debug3: key_read: no space
debug3: key_read: no space
debug3: key_read: no space
debug3: key_read: no space
debug3: key_read: no space
debug3: key_read: no space
debug3: key_read: no space
debug3: key_read: no space
debug3: key_read: no space
debug3: key_read: no space
debug2: key_type_from_name: unknown key type '-----END'
debug3: key_read: no key found

you shouldn't have -----BEGIN, ------END in your private key file...
that's all very suspicious. i'd take a look at the id_rsa_backup file and
see if it's been trashed somehow. it should be a binary file (the .pub
file is text)

er... ignore me Smile i obviously haven't looked at one of these files in a
very long time. -----BEGIN/END is normal in a v2 private key file... but
it really does look like the problem is your ssh is using v1 of the
protocol, and you're giving it a v2 key.

-dean

Post problems with unattended backup 
On 7 Jul 2004, Carlos Costa Portela <ccosta < at > smartec.es> wrote:
Hello all!

I'm using rdiff-backup, and all runs ok, but I cannot do unattended
backup. I've read the doc at
http://www.arctic.org/~dean/rdiff-backup/unattended.html (excellent doc,
btw), without luck. Here is the output of the ssh -C command:

OpenSSH_3.4p1 Debian 1:3.4p1-1.woody.3, SSH protocols 1.5/2.0, OpenSSL
0x0090603f
debug1: Reading configuration data /root/.ssh/config
debug1: Applying options for powerfull
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Rhosts Authentication disabled, originating port will not be
trusted.
debug1: ssh_connect: needpriv 0
debug1: Connecting to powerfull [192.168.1.70] port 22.
debug1: Connection established.
debug3: Not a RSA1 key file /root/.ssh/id_rsa_backup.
debug2: key_type_from_name: unknown key type '-----BEGIN'

I think you are using a public key where you should be using a private
key file, or RSA for DSA, or something like that.

As Dean says, get logins working before you introduce rdiff-backup.

--
Martin

Display posts from previous:
Reply to topic Page 1 of 1
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
  


Magic SEO URL for phpBB