bugrdiff-backup - Bugs: bug #30663, umask of backup user will not be...


bug #30663: umask of backup user will not be processed correctly

Submitted by:  None
Submitted on:  Thu 05 Aug 2010 08:11:55 PM UTC  
Category:  None Severity:  3 - Normal
Item Group:  None Status:  None
Privacy:  Public Assigned to:  None
Open/Closed:  Open

Add a New Comment (Rich Markup)

You are not logged in

Please log in, so followups can be emailed to you.


Thu 05 Aug 2010 08:11:55 PM UTC, original submission:  


To make the backup strategy more secure, it is often useful to make one user for doing the backups, and other users only are in some read only groups which can restore backups but not change the backed up files.

This can in general easily accomplished by having a umask of the backup creation user of 0027, so the group has only execute and read rights.

The Problem is, that rdiff backup changes the default linux users umask, and give most files in the backup NO permissions to the group. So all restoring users which were in the restoring group which should normaly have read only permissions have due to this behavior NO permissions.

So this, IMHO, more secure strategy of seperating backup user and restore user is not supportet in rdiff-backup version 1.2.8




(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:

No files currently attached


Depends on the following items: None found

Items that depend on this one: None found


Carbon-Copy List
  • -email is unavailable- added by ceelian

    Do you think this task is very important?
    If so, you can add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.




    Follows 1 latest change.

    Date Changed by Updated Field Previous Value => Replaced by
    2010-08-05 ceelian Carbon-Copy- => Added ceelian

    Back to the top

    Powered by Savane 3.5