From 47ece2c3c1f93268177e4876cb8f1f808bd12903 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 6 Jul 2015 13:45:45 -0400 Subject: [PATCH] comment --- ...nt_14_5bb12e6fa51da00ecf48f2dee1bfb050._comment | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 doc/tips/using_Amazon_S3/comment_14_5bb12e6fa51da00ecf48f2dee1bfb050._comment diff --git a/doc/tips/using_Amazon_S3/comment_14_5bb12e6fa51da00ecf48f2dee1bfb050._comment b/doc/tips/using_Amazon_S3/comment_14_5bb12e6fa51da00ecf48f2dee1bfb050._comment new file mode 100644 index 0000000000..3d99cca80a --- /dev/null +++ b/doc/tips/using_Amazon_S3/comment_14_5bb12e6fa51da00ecf48f2dee1bfb050._comment @@ -0,0 +1,14 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 14""" + date="2015-07-06T17:42:28Z" + content=""" +@james, since your keyring apparenty contains your secret key, the problem +may be in the configuration of your gpg agent or pinentry program. If the agent +is unable to use pinentry for some reason, gpg will complain that the +secret key is unavailable since it is unable to get the passphrase to +unlock it. + +I had a similar problem with gpg2 the other day: + +"""]]