From 06c6e7e79c1948981676d9c45187ec506a5007c6 Mon Sep 17 00:00:00 2001 From: Thomas Waldmann Date: Fri, 12 Mar 2021 22:28:39 +0100 Subject: [PATCH] docs: add unsafe workaround to use an old repo copy, fixes #5722 --- docs/faq.rst | 25 +++++++++++++++++++++++++ 1 file changed, 25 insertions(+) diff --git a/docs/faq.rst b/docs/faq.rst index d78272c4c..3e0ae4034 100644 --- a/docs/faq.rst +++ b/docs/faq.rst @@ -93,6 +93,31 @@ Also, you must not run borg against multiple instances of the same repo See also: :ref:`faq_corrupt_repo` +"this is either an attack or unsafe" warning +-------------------------------------------- + +About the warning: + + Cache, or information obtained from the security directory is newer than + repository - this is either an attack or unsafe (multiple repos with same ID) + +"unsafe": If not following the advice from the previous section, you can easily +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 +trick you into AES counter reuse, trying to break your repo encryption. + +If you'ld decide to ignore this and accept unsafe operation for this repository, +you could delete the manifest-timestamp and the local cache: + +:: + + borg config repo id # shows the REPO_ID + rm ~/.config/borg/REPO_ID/manifest-timestamp + borg delete --cache-only REPO + +This is an unsafe and unsupported way to use borg, you have been warned. + Which file types, attributes, etc. are *not* preserved? -------------------------------------------------------