summaryrefslogtreecommitdiff
path: root/doc/bugs/gpg_error_on_android/comment_4_032f42235b7f26854e725041ca33384b._comment
diff options
context:
space:
mode:
Diffstat (limited to 'doc/bugs/gpg_error_on_android/comment_4_032f42235b7f26854e725041ca33384b._comment')
-rw-r--r--doc/bugs/gpg_error_on_android/comment_4_032f42235b7f26854e725041ca33384b._comment10
1 files changed, 0 insertions, 10 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
deleted file mode 100644
index 5fdfa8211..000000000
--- a/doc/bugs/gpg_error_on_android/comment_4_032f42235b7f26854e725041ca33384b._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!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?
-"""]]