Sorry. Indeed, you have to create a backuppc user with /home/backuppc as
home in your clients, and in your server if you don't have one yet.
Then generate keys for your server backuppc user:
backuppc$> ssh-keygen -t rsa
use ssh-copy-id to copy the pub key to each of the clients
backuppc$>ssh-copy-
Hi users,
I've been thinking about the response to
ssh -l root 192.168.1.101 whoami
with response of 'root'.
When I create the BackupPC key for the visudo method, to where should
BackupPC_id_rsa.pub be copied? If I put it in /root/.ssh, is that not
asking for phraseless root access?
I looked at
Hi, ken
1- You must replace with your server IP or name in
Host_Alias LOCAL =
something like
Host_Alias LOCAL = 192.168.1.101
> root <<--- Is this correct for the visudo method?
This is correct for the ssh command ( ssh -l root 192.168.1.101 )
Visudo (file sudoers) only care about wh
Hi Luis (and others),
I've taken a little time to study the visudo approach to running
BackupPC instead of using phrase-less keys for root logon at the client
machine. This is a much lower risk, indeed.
On Ubuntu, Vim is the default editor for visudo with Vim-tiny included
in the distribution.
