mirror/borg
1
0
Fork 0
mirror of https://github.com/borgbackup/borg.git synced 2025-01-31 19:52:22 +00:00
Code Issues Releases Wiki Activity

remove remainders of borg key migrate-to-repokey

Browse source
This commit is contained in:
Thomas Waldmann 2022-08-03 21:46:54 +02:00
parent 78230dd299
commit c3345fe423
2 changed files with 0 additions and 61 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

60
docs/usage/key_migrate-to-repokey.rst.inc
View file

@ -1,60 +0,0 @@
.. IMPORTANT: this file is auto-generated from borg's built-in help, do not edit!
.. _borg_key_migrate-to-repokey:
borg key migrate-to-repokey
---------------------------
.. code-block:: none
borg [common options] key migrate-to-repokey [options] [REPOSITORY]
.. only:: html
.. class:: borg-options-table
+-------------------------------------------------------+----------------+--+
| **positional arguments** |
+-------------------------------------------------------+----------------+--+
| | ``REPOSITORY`` | |
+-------------------------------------------------------+----------------+--+
| .. class:: borg-common-opt-ref |
| |
| :ref:`common_options` |
+-------------------------------------------------------+----------------+--+
.. raw:: html
<script type='text/javascript'>
$(document).ready(function () {
$('.borg-options-table colgroup').remove();
})
</script>
.. only:: latex
REPOSITORY
:ref:`common_options`
|
Description
~~~~~~~~~~~
This command migrates a repository from passphrase mode (removed in Borg 1.0)
to repokey mode.
You will be first asked for the repository passphrase (to open it in passphrase
mode). This is the same passphrase as you used to use for this repo before 1.0.
It will then derive the different secrets from this passphrase.
Then you will be asked for a new passphrase (twice, for safety). This
passphrase will be used to protect the repokey (which contains these same
secrets in encrypted form). You may use the same passphrase as you used to
use, but you may also use a different one.
After migrating to repokey mode, you can change the passphrase at any time.
But please note: the secrets will always stay the same and they could always
be derived from your (old) passphrase-mode passphrase.

1
setup_docs.py
View file

@ -315,7 +315,6 @@ class build_man(Command):
"key_change-location": "key",
"key_export": "key",
"key_import": "key",
"key_migrate-to-repokey": "key",
"export-tar": "tar",
"import-tar": "tar",
"benchmark_crud": "benchmark",