[rdiff-backup-users] --restrict-update-only behaviour

[Gerard van Dijnsen]

Hi all,

I have been succesfully making backups for some time now using the 
"--restrict-update-only" option on the server side as a forced command. 
However, restoring using this option leads to the following error:

Traceback (most recent call last):
 File "/usr/bin/rdiff-backup", line 23, in ?
   rdiff_backup.Main.Main(sys.argv[1:])
 File "/usr/lib/python2.3/site-packages/rdiff_backup/Main.py", line 
286, in Main
   take_action(rps)
 File "/usr/lib/python2.3/site-packages/rdiff_backup/Main.py", line 
266, in take_action
   elif action == "restore-as-of": Restore(rps[0], rps[1], 1)
 File "/usr/lib/python2.3/site-packages/rdiff_backup/Main.py", line 
493, in Restore
   restore_set_fs_globals(dest_rp)
 File "/usr/lib/python2.3/site-packages/rdiff_backup/Main.py", line 
534, in restore_set_fs_globals
   mirror_fsa = 
Globals.rbdir.conn.fs_abilities.get_fsabilities_restoresource(
 File "/usr/lib/python2.3/site-packages/rdiff_backup/connection.py", 
line 445, in __call__
   return apply(self.connection.reval, (self.name,) + args)
 File "/usr/lib/python2.3/site-packages/rdiff_backup/connection.py", 
line 367, in reval
   if isinstance(result, Exception): raise result
rdiff_backup.Security.Violation:
Warning Security Violation!
Bad request for function: fs_abilities.get_fsabilities_restoresource
with arguments: [<rdiff_backup.rpath.RPath instance at 0xb798bc0c>]

the "--restrict" and "--restrict-read-only" options however seem to give 
no problems. Is this the desired behaviour? I would think that it should 
be possible to restore with this option as it is defined in the man page 
as a --restrict with some extra restrictions on the write permissions. 
Apparently, there is also a restriction for reads, but this is not 
mentioned in the manpage... This may be unintentional and thus a bug. 
Thought I'd mention it...

Cheers,

Gerard van Dijnsen