|
From: | Adam Pribyl |
Subject: | Re: [Duplicity-talk] Archive files permissions, extra logging |
Date: | Tue, 10 Nov 2020 11:53:16 +0100 (CET) |
User-agent: | Alpine 2.21 (DEB 202 2017-01-01) |
On Tue, 10 Nov 2020, edgar.soldin--- via Duplicity-talk wrote:
On 11/10/2020 9:14, Adam Pribyl via Duplicity-talk wrote:Is there a way to change the permissions for the archive files created by duplicity? It looks to me like this is hardcoded into the duplicity as there is def do_backup(action) ... os.umask(0o77) ... so it always creates the files with 600 (only user read/write),sounds reasonable as we do not want temporary/cache files created which potentially contain private data that are readable to anybody else. why would anybody else then the duplicity user who created them need access to these files?
Maybe I did not used the proper naming for "archive files" - for duplicity cache it is probably ok, but for backup files.. I'd like to e.g. have a group of users able to extract the files from backups, but I have to post-process the archives to add them group readability at least.
Extra logging in the def list_current(col_stats): ... user_info = u"%s %s %s" % (dup_time.timetopretty(path.getmtime()), path.type, util.ufn(path.get_relative_path())) log_info = "%s %s %s" % (dup_time.timetostring(path.getmtime()), util.escape(path.get_relative_path()), path.type) log.Log(user_info, log.INFO, log.InfoCode.file_list, log_info, True) but I did not found how to achieve the log_info to be printed. I can not make sens out of log.Log function "extra" argument...did you try raising verbosity to 'info' as described on http://duplicity.nongnu.org/vers8/duplicity.1.html ?
Yes, I did play with verbosity. Maybe I expect something different to happen, but the line with the file listed via the list-current-files remains the same. I thought it would add this extra info to eache line.
..ede/duply.net
Thanks anyway Adam Pribyl
[Prev in Thread] | Current Thread | [Next in Thread] |