diff options
author | Joey Hess <joeyh@joeyh.name> | 2015-07-06 13:45:45 -0400 |
---|---|---|
committer | Joey Hess <joeyh@joeyh.name> | 2015-07-06 13:45:45 -0400 |
commit | 1fbd532098e8537a407aec7df17192cdf8fd84b0 (patch) | |
tree | 318d7c02bed56887afc482676b2a0defcd8bc6c7 /doc/tips | |
parent | 2f0f0c349d3974b783dec6e58131de29dfd83867 (diff) |
comment
Diffstat (limited to 'doc/tips')
-rw-r--r-- | doc/tips/using_Amazon_S3/comment_14_5bb12e6fa51da00ecf48f2dee1bfb050._comment | 14 |
1 files changed, 14 insertions, 0 deletions
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 000000000..3d99cca80 --- /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: +<http://bugs.debian.org/791379> +"""]] |