From: Simon Hirscher <public@simonhirscher.de>
To: notmuch@notmuchmail.org
Subject: [BUG] Decryption fails if message was signed with an unknown key
Date: Thu, 5 Sep 2013 00:01:58 +0200 [thread overview]
Message-ID: <CAEj42wtt9O1-k9hm9DNCh7En=b-eDYQWham5-FR-wzrt+sij+g@mail.gmail.com> (raw)
Dear notmuch developers,
This is now the second time the following has happened to me:
#########
$ notmuch show --decrypt id:xyz@example.com
message{ id:xyz@example.com depth:0 match:1 excluded:0 filename:/home/simon/***
header{
John Doe <sender@example.com> (Today 21:52) (encrypted inbox new)
Subject: foobar
From: John Doe <sender@example.com>
To: ***
Date: Thu, 01 Jan 1970 00:00:00 +0000
header}
body{
Failed to decrypt part: gpg: ASCII-Hülle: Version: GnuPG v2.0.17 (MingW32)
gpg: <list of keys the message was encrypted with>
gpg: AES256 encrypted data
gpg: Original file name=''
gpg: Signature from Thu 01 Jan 1970 00:00:00 UTC by DSA key ID <sender's key>
gpg: Signature cannot be verified. Public key not found
part{ ID: 1, Content-type: multipart/encrypted
part{ ID: 2, Content-type: application/pgp-encrypted
Non-text part: application/pgp-encrypted
part}
part{ ID: 3, Filename: encrypted.asc, Content-type: application/octet-stream
Non-text part: application/octet-stream
part}
part}
body}
message}
$ gpg --recv-keys <sender's key>
$ notmuch show --decrypt id:xyz@example.com
[…]
Hey there,
Now the decryption worked!
[…]
############
Also, I should add that manually decrypting the message with gpg (i.e.
without using notmuch) already worked *before* I added the sender's
key (not shown above). Still, notmuch obviously doesn't like it when
the sender is unknown.
I hope you're going to look into this. Thank you!
next reply other threads:[~2013-09-04 22:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-04 22:01 Simon Hirscher [this message]
2013-09-05 15:03 ` [BUG] Decryption fails if message was signed with an unknown key Daniel Kahn Gillmor
2013-09-23 23:23 ` Simon Hirscher
2013-09-24 23:14 ` Daniel Kahn Gillmor
2013-09-10 11:29 ` David Bremner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAEj42wtt9O1-k9hm9DNCh7En=b-eDYQWham5-FR-wzrt+sij+g@mail.gmail.com' \
--to=public@simonhirscher.de \
--cc=notmuch@notmuchmail.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).