key_change-algorithm.rst.inc 3.2 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576
  1. .. IMPORTANT: this file is auto-generated from borg's built-in help, do not edit!
  2. .. _borg_key_change-algorithm:
  3. borg key change-algorithm
  4. -------------------------
  5. .. code-block:: none
  6. borg [common options] key change-algorithm [options] [REPOSITORY] ALGORITHM
  7. .. only:: html
  8. .. class:: borg-options-table
  9. +-------------------------------------------------------+----------------+----------------------+
  10. | **positional arguments** |
  11. +-------------------------------------------------------+----------------+----------------------+
  12. | | ``REPOSITORY`` | |
  13. +-------------------------------------------------------+----------------+----------------------+
  14. | | ``ALGORITHM`` | select key algorithm |
  15. +-------------------------------------------------------+----------------+----------------------+
  16. | .. class:: borg-common-opt-ref |
  17. | |
  18. | :ref:`common_options` |
  19. +-------------------------------------------------------+----------------+----------------------+
  20. .. raw:: html
  21. <script type='text/javascript'>
  22. $(document).ready(function () {
  23. $('.borg-options-table colgroup').remove();
  24. })
  25. </script>
  26. .. only:: latex
  27. REPOSITORY
  28. ALGORITHM
  29. select key algorithm
  30. :ref:`common_options`
  31. |
  32. Description
  33. ~~~~~~~~~~~
  34. Change the algorithm we use to encrypt and authenticate the borg key.
  35. Important: In a `repokey` mode (e.g. repokey-blake2) all users share the same key.
  36. In this mode upgrading to `argon2` will make it impossible to access the repo for users who use an old version of borg.
  37. We recommend upgrading to the latest stable version.
  38. Important: In a `keyfile` mode (e.g. keyfile-blake2) each user has their own key (in ``~/.config/borg/keys``).
  39. In this mode this command will only change the key used by the current user.
  40. If you want to upgrade to `argon2` to strengthen security, you will have to upgrade each user's key individually.
  41. Your repository is encrypted and authenticated with a key that is randomly generated by ``borg init``.
  42. The key is encrypted and authenticated with your passphrase.
  43. We currently support two choices:
  44. 1. argon2 - recommended. This algorithm is used by default when initialising a new repository.
  45. The key encryption key is derived from your passphrase via argon2-id.
  46. Argon2 is considered more modern and secure than pbkdf2.
  47. 2. pbkdf2 - the legacy algorithm. Use this if you want to access your repo via old versions of borg.
  48. The key encryption key is derived from your passphrase via PBKDF2-HMAC-SHA256.
  49. Examples::
  50. # Upgrade an existing key to argon2
  51. borg key change-algorithm /path/to/repo argon2
  52. # Downgrade to pbkdf2 - use this if upgrading borg is not an option
  53. borg key change-algorithm /path/to/repo pbkdf2