X-Git-Url: https://git.stderr.nl/gitweb?a=blobdiff_plain;f=FAQ;fp=FAQ;h=16a411e6e09659f136de3eadba96c8b03c3968a3;hb=ea9814ad2b78a7603d2b6f1b2916dc895aab9bd5;hp=0000000000000000000000000000000000000000;hpb=a76cc2f57605db3b3079baccd06c89466b6d2d30;p=matthijs%2Fupstream%2Fbackupninja.git

diff --git a/FAQ b/FAQ
new file mode 100644
index 0000000..16a411e
--- /dev/null
+++ b/FAQ
@@ -0,0 +1,19 @@
+Q: duplicity works fine when run standalone, but complains about gpg
+"public key not found" when run from backupninja
+
+A: We bet you're using sudo to run both duplicity and backupninja, and have been
+using sudo as well when generating the GnuPG key pair used by duplicity.
+
+Quick fix: generate a new GnuPG key pair in a root shell, or using
+"sudo -H" instead of plain sudo.
+
+Another solution: import the GnuPG keypair into the root user's keyring, taking
+care of running "gpg --update-trustdb" in a root shell or using "sudo -H"
+afterwards, in order to tag this keypair as "ultimately trusted".
+
+Detailed explanation: sudo does not change $HOME by default, so GnuPG saved the
+newly generated key pair to your own keyring, rather than to the root user's
+keyring. Running "sudo duplicity" hides the problem, as it uses your own
+keyring. Running "sudo backupninja" reveals the problem, as backupninja uses
+"su" to make sure it runs duplicity in a real root environment, i.e. using the
+root user's GnuPG keyring.