diff options
| author | TW <tw@waldmann-edv.de> | 2017-10-26 07:29:57 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2017-10-26 07:29:57 +0200 |
| commit | 5b1a170ec22650c1b83b36d3b814025cce4e9f06 (patch) | |
| tree | cd26aab87bd4094dc2c368b2e970a8b26d16501b | |
| parent | 46c071ca478b9585e25399f57b4977c4c302819a (diff) | |
| parent | 87a9952f3b78fddb089784e97e20ec66aebda0f6 (diff) | |
Merge pull request #3219 from milkey-mouse/keyfile-docs
Clarify using a blank passphrase in keyfile mode
| -rw-r--r-- | docs/faq.rst | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/docs/faq.rst b/docs/faq.rst index 6726e15bc..442df6f66 100644 --- a/docs/faq.rst +++ b/docs/faq.rst @@ -304,7 +304,7 @@ Setting ``BORG_PASSPHRASE`` .. _password_env: .. note:: Be careful how you set the environment; using the ``env`` command, a ``system()`` call or using inline shell scripts - (e.g. ``BORG_PASSPHRASE=hunter12 borg ...``) + (e.g. ``BORG_PASSPHRASE=hunter2 borg ...``) might expose the credentials in the process list directly and they will be readable to all users on a system. Using ``export`` in a shell script file should be safe, however, as @@ -328,7 +328,8 @@ Using ``BORG_PASSCOMMAND`` with a properly permissioned file Using keyfile-based encryption with a blank passphrase It is possible to encrypt your repository in ``keyfile`` mode instead of the default - ``repokey`` mode and use a blank passphrase for the key file. See :ref:`encrypted_repos` + ``repokey`` mode and use a blank passphrase for the key file (simply press Enter twice + when ``borg init`` asks for the password). See :ref:`encrypted_repos` for more details. Using ``BORG_PASSCOMMAND`` with macOS Keychain |