3 ms·
I use a dedicated backup user, and setfacl does allow inheritance of its acl on newly created things. I can't look it up now but I'm sure a Google search will f
by elmerfud 2y ago
I use a dedicated backup user, and setfacl does allow inheritance of its acl on newly created things. I can't look it up now but I'm sure a Google search will find it. It can also prevent the 640 as well because those acls are different than the normal mask.
I think what you might be doing is applying a group acl instead of a user acl. In my setup I use normal Unix group permissions for some things, acls that apply group permissions for most things, but for homes I put my backup account as acl user permissions for read.
Could you use root? Sure, but you would need to evaluate the risk in that. As root is "do all the things" account. The backup account can still read all the things so you still have data loss exposure but it can't modify the things.
- EyebrowsWhite 2y agoI have found the inheritance method, just add `-d` option. But I can't find the way to prevent 640. I know it's not really read by all others, but sshd will prevent login with error `error: Permissions 0640 for '/etc/ssh/ssh_host_rsa_key' are too open.`. I have tried a lot of commands, but still can't resolve this.