borgbackup
improve authenticated mode docs
Have you checked borgbackup docs, FAQ, and open Github issues?
Yes
Is this a BUG / ISSUE report or a QUESTION?
QUESTION / ISSUE (possible - docs or in borg init output)
System information. For client/server mode post info for both machines.
Your borg version (borg -V).
borg 1.1.15
Operating system (distribution) and version.
Linux Mint 20.3 Una
Hardware / network configuration, and filesystems used.
N/A
How much data is handled by borg?
N/A
Full borg commandline that lead to the problem (leave away excludes and passwords)
borg init --encryption authenticated-blake2 <PATH> / borg init --encryption authenticated <PATH>
Describe the problem you're observing.
As indirectly mentioned in #4042 the authenticated and authenticated-blake2 encryption modes store the key material in the repo's config file. According to #4042 it is therefore currently not possible to recover from the loss of key material in the aforementioned modes. While borg init suggests that you should back up the key the documentation does neither mention nor explain this necessity.
Suggested resolution
Further effort should be made in the docs to explain to, especially new users, that, until #4042 gets resolved, loosing the key and (or in case the user did not understand that he has to back up the key, that is) the config file will render the repo inaccessible.
Can you reproduce the problem? If so, describe how. If not, describe troubleshooting steps you took before opening the issue.
Yes
