* martin f krafft <[EMAIL PROTECTED]> [071102 01:06]: > also sprach Micah Anderson <[EMAIL PROTECTED]> [2007.05.20.0114 +0200]: > > If you have people other than root who are writing to > > /etc/backup.d and you have added them to the 'admingroup' in the > > backupninja config, you wont have this problem. > > Yes, I will, because as members of the admingroup, those people will > be able to read and write files, but some ways of editing create new > inodes, which will then be unwantingly owned by the user and no > longer root.
The problem here is the development philosophy of backupninja is to make the tool really easy to use so that people who might otherwise not know what they are doing will backup their system. If we remove this check, then its very easy for someone to create a file that the world can read with password credentials or otherwise sensitive information exposed. Its easy to make mistakes and we dont want to enable people to make those mistakes. We dont want this development philosophy to be make the tool really easy to accidentally expose sensitive information. > The admingroup enhancement was splendid, thanks for that! One option might be to make the check see if the file is owned by root or the admingroup, and if so, to not complain. However doesn't it sort of concern you if your admins are not noticing when they are writing config files as their own uid, when they should be written as root? Micah
signature.asc
Description: Digital signature
