TW
Fixed in 1.4-maint. ^^
Dealing with .checkpoint archives (in manifest, DELs related to the archives) makes this quite a bit harder than: - if there were no checkpoint archives at all (not great if...
@enkore guess you mean diff between `borg list repo` current + previous. and `borg check --verify-data repo`. yeah, guess that would do it also (because the archive id is authenticating...
@textshell yes, there could be some checkpoint/bookmark feature for long running stuff like `borg check [--verify-data]` for scalability. For security against attackers this would be only needed to see if...
OK, so I guess we reduced this ticket to "introduce a do-not-overwrite-existing-chunks repo server mode".
@mist there is no current work on this, AFAIK. not sure whether the idea is detailled enough / proof-checked enough yet.
As you noticed already: not really effective against attacks.
A lot has changed in borg master branch ("borg2"), so quite some of the stuff that referred to borg 1.x does not apply there anymore. About auditing: giving --debug now...
There is no support for beta-to-beta or beta-to-release upgrades in the code. Alphas/Betas are for testing and you should use them **additionally** to your production backups. So, if "next beta"...
best is to delete them with the working borg version.