Axel Burri

Thanks, merged in: 9dfee7bc32f392a599164ae4c2a0c24d418751ef > Comparing the asciidoc and asciidoctor man pages, everything looks OK. I checked as well, there is subtle whitespace changes, and email addresses are shown in...

To be honest, I'm not (yet) very familiar with bcachefs, but I assume that things are quite different to btrfs. Some time ago I looked at supporting ZFS, and I...

Thanks, I'll try to merge this into ssh_filter_btrbk.sh as soon as I find some time. This was not a high priority for me, as no root access is needed for...

Note that for raw targets, there is no requirement to ssh as root. This making the support in ssh_filter_btrbk much less important, as access control can be managed via correct...

Thanks for reporting, I will leave this issue open for a while, at least until the regression is fixed in btrfs-progs. Sadly there is not much that I can do...

This has already been discussed in #41: "The reason why this is not implemented is security-related: If btrbk runs user-defined commands, it makes it possible for an attacker to run...

> A configuration file used by a root process should always have at most 755 to prevent such backdoor. You are completely right here. Actually it's already very wise to...

> Doing our own pre/post command before and after the full 'btrbk run' is too long of a time span. What you can do to minimize the duration: 1. freeze...

> A send failed, probably due to a network failure, and btrbk reports ERROR: Failed to parse subvolume detail (unsupported btrfs-progs). But as far as I can tell, the error...

> So, btrbk clean will kill off half my backups Can you give an example on why it kills half your backups? `btrbk clean` should really only remove unfinished (garbled)...