mirror/borg
1
0
Fork 0
mirror of https://github.com/borgbackup/borg.git synced 2024-12-26 17:57:59 +00:00
Code Issues Releases Wiki Activity

docs: not only attack/unsafe, can also be a fs issue, fixes #7853

Browse source
This commit is contained in:
Thomas Waldmann 2023-11-01 17:40:47 +01:00
parent 1f48e500f2
commit 4325656f4c
No known key found for this signature in database
GPG key ID: 243ACFA951F78E01
1 changed files with 3 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

3
docs/faq.rst
View file

@ -86,6 +86,9 @@ run into this by yourself by restoring an older copy of your repository.
"attack": maybe an attacker has replaced your repo by an older copy, trying to "attack": maybe an attacker has replaced your repo by an older copy, trying to
trick you into AES counter reuse, trying to break your repo encryption. trick you into AES counter reuse, trying to break your repo encryption.
Borg users have also reported that fs issues (like hw issues / I/O errors causing
the fs to become read-only) can cause this warning, see :issue:`7853`.
If you decide to ignore this and accept unsafe operation for this repository, If you decide to ignore this and accept unsafe operation for this repository,
you could delete the manifest-timestamp and the local cache: you could delete the manifest-timestamp and the local cache: