Score:0

starting out w/ rdiff-backup, having permissions issues

jp flag

I have 2 machines - SERVER and BACKUP. On SERVER I have a script that backs up a few directories and databases, ending up in /var/local/backup with permissions intact (ownership is root and www-data on all of the files).

I'd like to use rdiff-backup on BACKUP to retrieve the contents of /var/local/backup on SERVER and sync it to, for example, /var/local/backup on BACKUP.

I have a user on both machines, USER1, and can ssh from BACKUP into SERVER as USER1; but USER1 cannot read the contents of /var/local/backup on SERVER nor write to /var/local/backup locally on BACKUP.

I would strongly prefer to not allow root access via ssh and I'd prefer not to chown/ chgrp the entirety of the files placed in /var/local/backup on SERVER.

My first thought was to add USER1 to the www-data group but that strikes me as possibly unwise from a security standpoint and doesn't address access to files owned by root.

I am at a loss and am beginning to suspect that there is an elegant answer out there. I would appreciate it if someone could point me toward it.

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.