From a7a478a19ead449fe02f737f169d189dc702a744 Mon Sep 17 00:00:00 2001 From: Alexander Neumann Date: Sat, 23 Sep 2017 19:15:21 +0200 Subject: [PATCH] doc: Correct FAQ --- doc/faq.rst | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/doc/faq.rst b/doc/faq.rst index b0e8495aa..8ddbce66f 100644 --- a/doc/faq.rst +++ b/doc/faq.rst @@ -32,13 +32,14 @@ How can I specify encryption passwords automatically? When you run ``restic backup``, you need to enter the passphrase on the console. This is not very convenient for automated backups, so you -can also provide the password through the ``--password-file`` option -or ``RESTIC_PASSWORD`` environment. A discussion is in progress over -implementing unattended backups happens in :issue:`533`. +can also provide the password through the ``--password-file`` option, or one of +the environment variables ``RESTIC_PASSWORD`` or ``RESTIC_PASSWORD_FILE`` +environment variables. A discussion is in progress over implementing unattended +backups happens in :issue:`533`. .. important:: Be careful how you set the environment; using the env command, a `system()` call or using inline shell - scripts (e.g. `RESTIC_PASSWORD=password borg ...`) + scripts (e.g. `RESTIC_PASSWORD=password restic ...`) 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