Hi Christian, The idea is nice, but I think it shall be configurable. If BiT is taking this backup to a remote location or any remote server is accessing this backup for anything, then it'll require a user matching the UID:GID numbers on the other side to continue executing the automation at the other hand. I can think of a number of scenarios where a cron job is accessing "last_snapshot" directory to take a look into a couple of files for some random task, or the remote server might run "du" on that folder tree to check for total size. Of course you can first make the change, and add the configuration capability if enough people report problems, that's a valid way to handle it, too. So, I personally prefer 0700 permissions, but some people might be doing interesting things, so be careful, I may say. Cheers, Hakan On 6/26/25 5:08 PM, c.buhtz@posteo.jp wrote:

Hey folks, I am interested in your opinions.

Currently the backup destination folder get its permissions from the operating systems umask settings. There is a 14 year old issue (<https://github.com/bit-team/backintime/ issues/377>) requesting to change that behavior.

Are there any concerns or objections against that BIT set by default the permissions to 0700 (rwx------) for the backup destination?

Regards, Christian _______________________________________________ Bit-dev mailing list -- bit-dev@python.org To unsubscribe send an email to bit-dev-leave@python.org https://mail.python.org/mailman3//lists/bit-dev.python.org Member address: hakan@bayindir.org