On 28/05/14 19:56, Holger Parplies wrote: > Hi, > > backu...@kosowsky.org wrote on 2014-05-27 19:30:26 -0400 [Re: > [BackupPC-users] Backuppc won't backup a remote system]: >> J.L. Blom wrote at about 23:46:43 +0200 on Tuesday, May 27, 2014: >> > [...] >> > All, >> > Thanks for the responses. I'll answer below. >> > XIN, : Yes I can ssh to the remote system; >> > DAVID: yes I have to give the password; >> > TAN: No I logged on as the user on that system with the corresponding >> > password; >> > Explain MOTD (?); >> Message of the day. > to be a little bit more verbose, for the backup to work, you need to be able > to see the following (the prompt text and exact date/time may differ): > > backuppc@your-backuppc-server% ssh -c blowfish -q -x -l USER SYSTEM date > Wed May 28 19:36:42 CEST 2014 > backuppc@your-backuppc-server% > > If there's any more than that (e.g. password prompt, "last login" line, some > sort of "Welcome to ...", even a blank line or a single space character before > the date), it's not going to work. This is not your current problem, but it > might be the next one to come. > > (Disclaimer: if you've got a "command=..." option in your authorized keys, > that probably won't work. But you probably don't. If you don't know what I'm > talking about, just ignore it, it doesn't apply then.) > >> > TAN: I logged on with backuppc and it asked for the password so I think >> > that is the problem > Correct. > >> > but how to solve it? > As has been pointed out, there are many guides. In a nutshell, you need an > ssh key (that is *not* protected by a passphrase), that the *backuppc user* on > the *BackupPC server* has access to, and that has permission to login as USER > on SYSTEM (to use the terms from your original mail), i.e. the public key > needs > to be in SYSTEM:~USER/.ssh/authorized_keys (see sshd(8) for details). > >> How would you expect BackupPC to possibly log on to the client if it >> requires a password? BackupPC does not magically 'crack' passwords or >> hack its way onto your machine... > Feature request? ;-) > >> It's also customary to read the instructions and/or FAQ before >> bombarding the whole list with questions > Actually, the list bombarded him with questions :-). But yes, the first > (obviously off-list) reply did contain the correct information. Saying "no, > that's not it", when it actually is, makes helping a little difficult ... > > Regards, > Holger Holger, Thanks for your lucid reply. with respect to the remark of Gopu Krishnan it is neither help- or respectful. He has no inkling of an idea of my knowledge about systems and even if I were completely ignorant it is not the way to address people on an email-list.
Your help is welcome as I have never studied the internal workings of the security of ssh and the like, i.e. never studied PGP when it first appeared,( I think around 1983). I will work out the things you mentioned I'I already found that I have no .ssh/authorized_keys file on my local system but backuppc happily does a backup, while on the USER SYSTEM this file exist but it lack the file known_hosts. I can login to that system but need a password. There is apparently something I have to repair on, I assume, my system to get the key-pair to work. So back to reading the ssh manual/tutorial to get it all correct. If you have any tips you're of course welcome! Thanks again, Joep ------------------------------------------------------------------------------ Time is money. Stop wasting it! Get your web API in 5 minutes. www.restlet.com/download http://p.sf.net/sfu/restlet _______________________________________________ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List: https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki: http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/