-
Notifications
You must be signed in to change notification settings - Fork 147
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add UI for borg key backup #1918
Comments
In the current version of Vorta it is easy to export the settings on a per-profile base. Doing this, the users are asked if the repo passphrase should be included to the settings ( .json) file. Currently Vorta does not try to "educate" the user about best practice. Perhaps it is a good idea to actively promote to "save the profile settings" including the repo "passphrase" and "export keys" and to store these savely (e.g. password manager) and keep a copy at a save place (i.e. out side your computer or even building)? |
I just tested the behaviour, using Vorta 9.1.
|
@goebbe borg emits these hints at |
@ThomasWaldmann exactly. I tried to test if Vorta passes the information/ warning about the keys to the user. If I understand correctly, users should be encouraged to make a backup of the borg keyfile, when initializing a repo. I believe there are two distinct steps:
By the way, these are the relevant lines from the log files, when initialising, using keyfiles:
edit: |
The step to create a key backup is the same no matter whether keyfile or repokey is used and the backup should be made in both cases. |
@ThomasWaldmann In the case of a (local) keyfile: Would it be sufficient to just copy/ backup the keyfile directly from Related question: When restoring, using Vorta from a different computer, with a (local) keyfile: Would it be sufficient to just copy the keyfile to |
Same for No manual key file copying. |
Related: #599 from @samu-w |
The problem
Now and then I get contacted by borg users who have lost the borg key, asking for help with regaining access to their archived data.
Of course there is no way to do that if the key is really lost - that would be a severe security issue if that was possible.
So the only option is to try to recover the deleted key and that is usually rather complicated and often not successful:
usage of "undelete" tools for local filesystems, hoping the storage device block(s) with the key have not yet been overwritten or discarded.
sometimes users directly back up onto FUSE-mounted cloud storage. if they don't have file versioning activated there, guess it is impossible to recover a file from a bucket. otoh, having versioning active might be a bad idea concerning space usage and related costs, because borg compact moves around a lot of data.
So, users should be motivated to have a borg key backup.
borg init
tells them every time to do that.Does vorta also tell them? Vorta should also actively help them doing that.
Requested Solution
Add a UI wrapping
borg key export
(and maybe alsoborg key import
later).Guess the best way would be to use the option creating that html page with the QR code and the key hexdump and then invoke the default browser showing that html file.
The text was updated successfully, but these errors were encountered: