From: intrigeri <intrigeri@758a04ac-41e6-0310-8a23-8373a73cc35d>
Date: Tue, 9 Dec 2008 10:56:15 +0000 (+0000)
Subject: FAQ: new file, with first Q/A for duplicity vs. sudo related issues
X-Git-Url: https://git.stderr.nl/gitweb?a=commitdiff_plain;h=47a07de9508002a4543d88f3f03b03f1c783d816;p=matthijs%2Fupstream%2Fbackupninja.git

FAQ: new file, with first Q/A for duplicity vs. sudo related issues

git-svn-id: http://code.autistici.org/svn/backupninja/trunk@627 758a04ac-41e6-0310-8a23-8373a73cc35d
---

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.