Skip to content

Commit

Permalink
document insecure-no-password
Browse files Browse the repository at this point in the history
  • Loading branch information
MichaelEischer committed May 18, 2024
1 parent d7287c0 commit 27ee44a
Show file tree
Hide file tree
Showing 2 changed files with 42 additions and 0 deletions.
19 changes: 19 additions & 0 deletions changelog/unreleased/issue-1786
Original file line number Diff line number Diff line change
@@ -0,0 +1,19 @@
Enhancement: Support repositories with empty password

Restic refused to create or operate on repositories with an emtpy password.
Using the new option `--insecure-no-password` it is now possible to disable
this check. Restic will not prompt for a password when using this option.
For security reasons, the option must always be specified when operating on
repositories with an empty password.

Specifying `--insecure-no-password` while also passing a password to restic
via a CLI option or via environment variable results in an error.

The `init` and `copy` command also support the option `--from-insecure-no-password`
which applies to the source repository. The `key add` and `key passwd` comands
include the `--new-insecure-no-password` option to add or set and emtpy password.

https://github.com/restic/restic/issues/1786
https://github.com/restic/restic/issues/4326
https://github.com/restic/restic/pull/4698
https://github.com/restic/restic/pull/TODO
23 changes: 23 additions & 0 deletions doc/030_preparing_a_new_repo.rst
Original file line number Diff line number Diff line change
Expand Up @@ -846,3 +846,26 @@ and then grants read/write permissions for group access.
.. note:: To manage who has access to the repository you can use
``usermod`` on Linux systems, to change which group controls
repository access ``chgrp -R`` is your friend.


Repositories with empty password
********************************

Restic by default refuses to create or operate on repositories that use an
empty password. Since restic 0.17.0, the option ``--insecure-no-password`` allows
disabling this check. Restic will not prompt for a password when using this option.
Specifying ``--insecure-no-password`` while also passing a password to restic
via a CLI option or via environment variable results in an error.

For security reasons, the option must always be specified when operating on
repositories with an empty password. For example to create a new repository
with an empty password, use the following command.

.. code-block:: console
restic --insecure-no-password init
The ``init`` and ``copy`` command also support the option ``--from-insecure-no-password``
which applies to the source repository. The ``key add`` and ``key passwd`` comands
include the ``--new-insecure-no-password`` option to add or set and emtpy password.

0 comments on commit 27ee44a

Please sign in to comment.