summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar http://joeyh.name/ <http://joeyh.name/@web>2013-07-09 18:03:13 +0000
committerGravatar admin <admin@branchable.com>2013-07-09 18:03:13 +0000
commit7225ac97f2f82754dce533142e283420dfa052b4 (patch)
tree7ec0c87a1a01dae79cdbdf56200e459e88c69c52
parentb14b041bfa448dff6a486b3e04910741732b8c0e (diff)
Added a comment
-rw-r--r--doc/bugs/gpg_error_on_android/comment_4_032f42235b7f26854e725041ca33384b._comment10
1 files changed, 10 insertions, 0 deletions
diff --git a/doc/bugs/gpg_error_on_android/comment_4_032f42235b7f26854e725041ca33384b._comment b/doc/bugs/gpg_error_on_android/comment_4_032f42235b7f26854e725041ca33384b._comment
new file mode 100644
index 000000000..5fdfa8211
--- /dev/null
+++ b/doc/bugs/gpg_error_on_android/comment_4_032f42235b7f26854e725041ca33384b._comment
@@ -0,0 +1,10 @@
+[[!comment format=mdwn
+ username="http://joeyh.name/"
+ ip="4.154.7.235"
+ subject="comment 4"
+ date="2013-07-09T18:03:12Z"
+ content="""
+So, I am able to get the \"bad\" key message out of gpg if I encrypt with --symmetric with a passphrase and then enter the wrong passphrase when decrypting.
+
+Perhaps git-annex is sending gpg the wrong encryption key, or perhaps the git repo it's operating in has an old version of the key for this remote somehow?
+"""]]