Diff
1diff --git a/duplicity-backup.conf.example b/duplicity-backup.conf.example
2index b3af280edfb3e1c29676a10f531f3594d4ef2cfe..448a73e1471480399c119bba54fb3f3b4ca61c37 100644
3--- a/duplicity-backup.conf.example
4+++ b/duplicity-backup.conf.example
5@@ -50,17 +50,20 @@ ENCRYPTION='yes'
6
7 # If you are NOT running this from a cron, comment this line out
8 # and duplicity should prompt you for your password.
9-# Otherwise this password is either used for symetric encryption
10+# Otherwise this password is either used for symmetric encryption
11 # (your backups will be encrypted with this password) or is used
12 # for the "GPG_SIGN_KEY" (see below).
13 # Comment out if you aren't using encryption
14 PASSPHRASE="foobar_gpg_passphrase"
15
16 # Specify which GPG keys you would like to use (even if you have only one).
17-# It is highly recommended to create separate signature and encryption keys.
18-# When run, duplicity should prompt you for the GPG_SIGN_KEY password
19-# (or specify the PASSPHRASE above if you run this script from a cron).
20-# Comment out if you're using only PASSPHRASE (symetric encryption) or not using
21+# If you are running this from a cron, it is highly recommended to create separate
22+# signature and encryption keys, because you have to specify the password for the
23+# GPG_SIGN_KEY via the above PASSPHRASE variable
24+# (see http://www.debian-administration.org/articles/209#d0e109).
25+# If you are not running the script from a cron, duplicity should prompt you for the
26+# GPG_SIGN_KEY password.
27+# Comment out if you're using only PASSPHRASE (symmetric encryption) or not using
28 # encryption at all.
29 GPG_ENC_KEY="foobar_gpg_key"
30 GPG_SIGN_KEY="foobar_gpg_key"