Displaying 3 results from an estimated 3 matches for "name_is_exclud".
Did you mean:
name_is_excluded
2017 Oct 31
2
[Bug 13112] New: receive_xattr heap overread with non null terminated name and xattr filter
...ends the length of
the name, and then sends the name. The name is read in via read_buf so it's not
null terminated.
815 size_t name_len = read_varint(f);
826 read_buf(f, name, name_len);
If the sender sent --filter that had an xattr filter then this name will be
passed to name_is_excluded.
834 if (saw_xattr_filter) {
835 if (name_is_excluded(name, NAME_IS_XATTR, ALL_FILTERS)) {
This can lead to a heap overread as name_is_excluded is expecting a NULL
terminated string.
These are the arguments I'm sending to the daemon when connecting
{"--server&q...
2019 Mar 22
2
Kudos and feature question
Kudos all that maintain this awesome and enduring piece of software. Awesome job, many thanks.
I’ve come across a use case that would greatly benefit form a —delete-older-than <secs> argument. This would behave the same as —delete only sparing files dest that have a creating time less than <secs> ago. How hard would this be to implement? Where would I start ?
TIA,
Francois
2019 Mar 24
0
Kudos and feature question
...this rule to apply (which could just be a wildcard matching anything by default, but could also use the full pattern-matching capabilities if required).
Have a look at:
the 'make_backups' logic in parse_arguments(), where it adds a 'Preserve' pattern to match all backup files,
name_is_excluded() and its subfunctions check_filter() and rule_matches() in exclude.c
You'd need to:
define a new filter-type character ('R' for preserve-Recent?)
define the format of the filter rule for this type e.g. how to represent the time
add code to parse this new ruletype in rule_matches...