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

[anonymous]

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

I can verify that this is still a problem in 1.1.14.  If you use the
--restrict-update-only option the first backup will fail.  So if you have a
server that's set to receive rdiff-backup pushes from clients you currently
have to set the server to --restrict for the first backup and then change it
to --restrict-update-only for subsequent backups.  The ideal behavior would be
to treat a first backup as an "update" and allow it to run as it does under
--restrict, that is still constrained to the specified directory.

In other words if you have rdiff restricted via ssh key to running as:

rdiff-backup --server --restrict-update-only /mnt/backups/

And the request is to backup to /mnt/backups/newserver then if the directory
/mnt/backups/newserver exists then process as happens now.  If it doesn't
exist then allow the creation of the first backup so long as the directory is
still within the one specified by the restrict statement.

    _______________________________________________________

Reply to this item at:

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

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