From: Trey D. <tre...@gm...> - 2012-12-30 23:59:12
|
On Dec 30, 2012 2:42 PM, "Tommi Huttunen" <tom...@gm...> wrote: > > I have successfully installed Backuppc and it's working when PermitRootLogin = yes is in the client's sshd_config. > I wouldn't want to do this, because it's quite insecure. > If I put PermitRootLogin = no into sshd_config, Backuppc is not working. > What would the best option to solve this? > > -Tommi > > ------------------------------------------------------------------------------ > Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, > MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current > with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft > MVPs and experts. ON SALE this month only -- learn more at: > http://p.sf.net/sfu/learnmore_123012 > _______________________________________________ > BackupPC-users mailing list > Bac...@li... > List: https://lists.sourceforge.net/lists/listinfo/backuppc-users > Wiki: http://backuppc.wiki.sourceforge.net > Project: http://backuppc.sourceforge.net/ > To more securely still use root set PermitRootLogin = without-password (double check syntax , on mobile device), so root can login ONLY via ssh keys. The above is easier if you have config management (ie Puppet) pushing keys. The other approach is a backuppc user on each backup target. Give that user sudo, without password, to your backup command (ie /usr/bin/rsync). Be sure to comment out require tty in sudoers file, or just for the backuppc local user. - Trey |