Yaakov,
The instructions I gave you below do not require the script that you
mention.
Here's an overview of what's going on. In order to back up a host, you
need to provide read access to the files you intend to back up. One way
of doing this is with 'sudo'. This gives temporary root permissio
On Sun, 22 Jul 2007 11:39:46 -0400, [EMAIL PROTECTED] said:
> It says:
> "In this case Josh NICES the backup so that it doesn't give such a
> performance hit on the client..."
> Then it give the command using "nice" as one of the command arguments.
>
> Can someone explain to me what this means?
Hi,
I was going through the documentation on this and there is something I
don't understand, probably due to my limited Linux knowledge...
It says:
"In this case Josh NICES the backup so that it doesn't give such a
performance hit on the client..."
Then it give the command using "nice" as one of
according to this link:
http://backuppc.sourceforge.net/faq/ssh.html#how_can_client_access_as_root_be_avoided
the /etc/sudoers line should have looked like this:
user_with_sudo_rights ALL=NOPASSWD: /usr/bin/rsync --server --sender *
-Rob
Yaakov Chaikin wrote:
> Which of the config directive nee
Assuming you're using rsync as the transport:
This is the default setting in config.pl
$Conf{RsyncClientCmd} = '$sshPath -q -x -l root $host $rsyncPath $argList+';
That needs to be changed to
$Conf{RsyncClientCmd} = '$sshPath -q -x -l username_with_sudo_rights
$host sudo $rsyncPath $argList+';
Which of the config directive needs to change for the "sudo" part and
how would it look? Could you give an example?
Thanks,
Yaakov.
On 7/18/07, Rob Owens <[EMAIL PROTECTED]> wrote:
> If you're going to connect to the host as root, then no changes to
> config.pl are needed. If you're going to con
Would this require a different configuration within the config.pl
file(s) within BackupPC itself? Or as far as BackupPC is concerned the
configuration can stay the same as if it has exchanged the rsa keys
with the user 'root'?
Thanks,
Yaakov.
On 7/13/07, Rob Owens <[EMAIL PROTECTED]> wrote:
> Kei
Keith Edmunds wrote:
> On Fri, 13 Jul 2007 09:39:15 -0400, [EMAIL PROTECTED] said:
>
>
>> The user would need read-access to everything (in order to backup /home
>> and some files in /etc), preferably without being able to run commands
>> other than rsync. How would I achieve this?
>>
>
On Fri, 13 Jul 2007 09:39:15 -0400, [EMAIL PROTECTED] said:
> The user would need read-access to everything (in order to backup /home
> and some files in /etc), preferably without being able to run commands
> other than rsync. How would I achieve this?
By using sudo (as I said). Sudo runs the
Keith Edmunds wrote:
> On Fri, 13 Jul 2007 09:24:25 -0400, [EMAIL PROTECTED] said:
>
>
>> So to summarize, I'm looking for a way to limit what root can do through
>> ssh. I'd appreciate any suggestions you folks could give me.
>>
>
> Don't use the root account to login. Use an ordinary
On Fri, 13 Jul 2007 09:24:25 -0400, [EMAIL PROTECTED] said:
> So to summarize, I'm looking for a way to limit what root can do through
> ssh. I'd appreciate any suggestions you folks could give me.
Don't use the root account to login. Use an ordinary user account, and
allow that account to run
I've been trying to figure out a good way of increasing the security
related to my backuppc ssh keys. I'm using rsync to backup Linux
machines over the internet, and backuppc is given root access to those
machines. I don't like allowing ssh access to root and I'm trying to
come up w/ a way to
12 matches
Mail list logo
