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

 
 

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

Submitter:  None
Submitted:  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:  Closed
* Mandatory Fields

Add a New Comment Rich Markup
   

Fri 20 May 2022 05:43:16 PM UTC, comment #1: 

This issue has been closed because it hasn't been touched for years, as the development continued on GitHub. If the issue is still present in a recent version, please re-open it under https://github.com/rdiff-backup/rdiff-backup/issues after having made that it's not already reported there.

Eric L. <ericzolf>
Group administrator
Thu 05 Aug 2010 08:11:55 PM UTC, original submission:  

Hello,

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

regards,
Christian

Anonymous

 

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

Attach Files:
   
   
Comment:
   

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 ericzolf (Posted a comment)
  • -email is unavailable- added by ceelian
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.

     

    Follow 2 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2022-05-20 ericzolf Open/ClosedOpen Closed
    2010-08-05 ceelian Carbon-Copy- Added ceelian

    Back to the top

    Powered by Savane 3.13-f8d8.
    Corresponding source code