From 9b89b5c1d22d50014a2c62076f3e8ade72673aa8 Mon Sep 17 00:00:00 2001 From: Ganwell Date: Thu, 14 Aug 2014 23:53:05 +0000 Subject: [PATCH] Added a comment: Problem solved --- .../comment_1_cce5e2c16720cc8e32a4a479f50ce6b3._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/forum/gcrypt_os_x_app_vs_brew/comment_1_cce5e2c16720cc8e32a4a479f50ce6b3._comment 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 0000000000..bcf094073d --- /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. +"""]]