TW
If somebody is finding this searching for a solution/workaround for borg 1.0/1.1: - you can exclude "known-big" files by a name-based pattern, like `*.iso` (or their directory, like `.../Virtualbox VMs/*`)....
Note: the first implementation could just limit the scope to size-based include/exclude (but when writing the code, do it in a way that e.g. timestamp-based can be easily done also).
In the end, guess this will need boolean expressions. Operators `and`, `or` and `not`. And the terms in these expressions would be stuff like: - size < 100M - mtime...
Yeah. Also this is a bit different to implement (one has to look at archived metadata vs. at stat() metadata from fs).
it is now (master branch, later borg 1.2) possible to feed `find` output (paths) into borg instead of using borg's builtin recursion. so you can do all matching/selecting that is...
``` borg create --paths-from-stdin or --paths-from-command ``` See there: https://borgbackup.readthedocs.io/en/1.2.0b3/usage/create.html
related: #4972
#8895 changed borg a bit: it now reads the simple `stat` attrs as well as xattrs and ACLs early, before processing file content. It now has some hardcoded stuff for...
I suspect this has the same issue as #6478. The problem is not only "not to keep keys in python objects" and "using secure memory for keys", but also that...
@Atharva-Varpe this might be a rather hard task with unsure outcome. Also, as of now (guess that was different when I opened it), there are no plans to add libsodium...