aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Ganwell <Ganwell@web>2014-08-14 23:53:05 +0000
committerGravatar admin <admin@branchable.com>2014-08-14 23:53:05 +0000
commite323aa9084d57ae7f98bd105849c048fcd8a8d6f (patch)
treeb209fdaf12ccf28a4c7783beeb7b4a35471e931d
parentae2aa6649b8fbcbd9c36efcf40aa45d0f3a0e55c (diff)
Added a comment: Problem solved
-rw-r--r--doc/forum/gcrypt_os_x_app_vs_brew/comment_1_cce5e2c16720cc8e32a4a479f50ce6b3._comment8
1 files changed, 8 insertions, 0 deletions
diff --git a/doc/forum/gcrypt_os_x_app_vs_brew/comment_1_cce5e2c16720cc8e32a4a479f50ce6b3._comment b/doc/forum/gcrypt_os_x_app_vs_brew/comment_1_cce5e2c16720cc8e32a4a479f50ce6b3._comment
new file mode 100644
index 000000000..bcf094073
--- /dev/null
+++ b/doc/forum/gcrypt_os_x_app_vs_brew/comment_1_cce5e2c16720cc8e32a4a479f50ce6b3._comment
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="Ganwell"
+ ip="178.174.3.221"
+ subject="Problem solved"
+ date="2014-08-14T23:53:05Z"
+ content="""
+It turns out gpgtools will save to wrong passphrase to the keychain without complaining. Thats why standard gpg worked and gpgtools didn't: There was a typo in the passphrase in the keychain.
+"""]]