| 1 |
On Nov 12, 2011 11:23 AM, "Michael Orlitzky" <michael@××××××××.com> wrote: |
| 2 |
> |
| 3 |
> On 11/11/2011 10:20 PM, Pandu Poluan wrote: |
| 4 |
> > |
| 5 |
> >> And if I pull, none of my backed-up systems are secure because anyone |
| 6 |
> >> who breaks into the backup server has root read privileges on every |
| 7 |
> >> backed-up system and will thereby "gain full root privileges quickly." |
| 8 |
> > |
| 9 |
> > IMO that depends on whether you also backup the authentication-related |
| 10 |
> > files or not. Exclude them from backup, ensure different root passwords |
| 11 |
> > for all boxes, and now you can limit the infiltration. |
| 12 |
> |
| 13 |
> If you're pulling to the backup server, that backup server has to be |
| 14 |
> able to log in to and read all files on the other servers. Including |
| 15 |
> e.g. your swap partition and device files. |
| 16 |
> |
| 17 |
|
| 18 |
Again, that's a matter of implementation. |
| 19 |
|
| 20 |
If the server doesn't access the client's filesystem directly but via an |
| 21 |
agent (Bacula does this, for instance), the server's access will be limited |
| 22 |
to what the agent provides. |
| 23 |
|
| 24 |
Rgds, |
Archives