From: Grant <emailgrant@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] {OT} rdiff-backup: push or pull?
Date: Thu, 18 Aug 2011 18:01:08 -0700 [thread overview]
Message-ID: <CAN0CFw0Dvyn2zz_QLS8zBucSVbJbkVoUeBBMZ5aVzK7yps+2Ug@mail.gmail.com> (raw)
In-Reply-To: <24789713.e3lGWgN6L7@eve>
>> >> > You can seperate the backups by giving each system a different
>> >> > account
>> >> > where to store the backups.
>> >>
>> >> I'm not sure what you mean. The backups are all stored on the backup
>> >> server.
>> >
>> > Each machine to be backed up has a different account on the backup
>> > server. This will prevent machine A from accessing the backups of
>> > machine B.
>> >
>> > This way, if one machine is compromised, only this machines backups can
>> > be accessed using the access-keys for the backup. And this machines
>> > keys can then be revoked without affecting other backups.
>>
>> That's a great idea. I will do that. Should that backup account have
>> any special configuration, or just a standard new user?
>
> I would suspect just a standard new user with default permissions.
> Eg. only write-access to his/her own files.
>
> And I'd prevent that user account from being able to get a shell-account.
I created the backup users and everything works as long as the backup
users have shells on the backup server and are listed in AllowUsers in
/etc/ssh/sshd_config on the backup server. Did I do something wrong
or should the backup users need shells and to be listed in AllowUsers?
Should I set up any extra restrictions for them in sshd_config?
Should I set passwords for them?
- Grant
> A ".bashrc" with "exit" as the last or first entry is a nice touch. Especially
> if you set the permissions such that it works for the user but the user can
> never change that file.
>
> --
> Joost
next prev parent reply other threads:[~2011-08-19 1:02 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-16 4:58 [gentoo-user] {OT} rdiff-backup: push or pull? Grant
2011-08-16 6:35 ` Joost Roeleveld
2011-08-16 23:50 ` Grant
2011-08-17 6:07 ` Joost Roeleveld
2011-08-17 17:18 ` Grant
2011-08-18 6:13 ` Joost Roeleveld
2011-08-19 1:01 ` Grant [this message]
2011-08-19 6:07 ` Joost Roeleveld
2011-08-19 17:13 ` Grant
2011-08-17 6:14 ` Joost Roeleveld
2011-08-17 17:35 ` Grant
2011-08-19 17:14 ` Michael Orlitzky
2011-08-19 18:00 ` Grant
2011-08-19 19:06 ` Michael Orlitzky
2011-08-19 19:58 ` Grant
2011-08-20 8:12 ` Alan McKinnon
2011-08-17 6:15 ` Joost Roeleveld
2011-08-17 17:37 ` Grant
2011-08-17 18:54 ` Alex Schuster
2011-08-17 20:47 ` Grant
2011-08-17 21:49 ` Alex Schuster
2011-08-17 22:03 ` Alan McKinnon
2011-08-18 0:35 ` Peter Humphrey
2011-08-18 6:30 ` Joost Roeleveld
2011-08-19 1:51 ` Grant
2011-08-19 6:13 ` Joost Roeleveld
2011-08-19 17:35 ` Grant
2011-08-21 19:10 ` Joost Roeleveld
2011-08-16 13:39 ` Bill Longman
2011-08-16 14:04 ` Alan McKinnon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAN0CFw0Dvyn2zz_QLS8zBucSVbJbkVoUeBBMZ5aVzK7yps+2Ug@mail.gmail.com \
--to=emailgrant@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox