[Rdiff-backup-bugs] [bug #16897] Security Violation on first increment while using restrict-update-only

[dean gaudet]

Follow-up Comment #5, bug #16897 (project rdiff-backup):

more thoughts on this... if i were to try to do a push backup system where
all the clients shared a common private key i think what i'd do on the server
is have the .ssh/authorized_keys command="foo" invoke a script of my own
(you'd probably need a remote-schema change too).

the script on the server would validate the SSH_CLIENT env var contains a
client which is supposed to be backed up, and then mkdir /mnt/backups/$IP as
necessary and finally exec rdiff-backup --server --restrict-update-only
/mnt/backups/$IP.

this way the clients can't trash each other easily (assuming rdiff-backup
--restrict-* are actually secure :)

but hey... go ahead and add os.mkdir i guess.

-dean

    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/bugs/?16897>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.nongnu.org/