* martin f krafft <[EMAIL PROTECTED]> [070516 06:48]: > Package: backupninja > Version: 0.9.4-6 > Severity: wishlist > > Configuration files must be owned by root! Dying on file > /etc/backup.d/90.sys > > In the light of #370396, this makes little sense as some editors > will write into a new inode and then the file will be owned by != > root. I appreciate the security checks in backupninja, but if the > sysadmin gives a person write access to the configuration files, > s/he knows what s/he's doing. backupninja should just do it's thing > now... IMHO.
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. I am slightly confused because you requested the feature to add the 'admingroup' function, included a patch and we fixed the patch up and included it (although it introduced some errors that we later had to fix, we fixed those), but now you are suggesting we through out that enhancement, as well as the original code altogether? Or am I missing something here? micah -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
