On Thursday, February 20, 2020 10:34:53 PM CET, Sebastian Andrzej Siewior
via rsync wrote:
I'm still not sure if rsync requires a cryptographic hash _or_ if a
strong hash like xxHash64 would be just fine for the job.
I'm fairly sure the hash should *not* be easy to spoof, so I'd say a
According to --help:
--fake-superstore/recover privileged attrs using xattrs
So I would assume which mode it uses when it reads the file,
depends on whether this option is on or off.
On Monday, March 16, 2020 9:09:36 PM CET, Kevin Korb via rsync wrote:
I don't believe it is
I don't believe it is possible. I think the misunderstanding stems from
the fact that the permissions are even stored in the xattr. They don't
need to be there but they may as well be. They don't take much space.
The real question would be when rsync reads the file to restore it and
the file
Thanks. This is a bit counter-intuitive to me. So how would you tell
rsync to store the original permissions in the xattr, but do not touch
the real file mode?
On Thursday, March 12, 2020 6:26:18 PM CET, Kevin Korb via rsync wrote:
I would expect that the sending rsync would only send the perms
schilytools star has the ability to restore ctimes from tarfiles. This
is useful when restoring filesystems as root in single user mode, and
I thought I'd like rsync to do the same.
I started working off the rsync-patches/atimes.diff patch but noticed
that this patch is buggy and presently does
