From: Jameson Graef Rollins <jrollins@finestructure.net>
To: Notmuch Mail <notmuch@notmuchmail.org>
Subject: decryption error for signed+encrypted messages
Date: Fri, 04 Nov 2011 11:00:19 -0700 [thread overview]
Message-ID: <87obwrix8s.fsf@servo.finestructure.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 666 bytes --]
I just wanted to note on-list that I've run into what I think is a GMIME
bug having to do with encrypted messages. I think this has been
mentioned on IRC, but I wanted to document it here (so that we can tag
it with our new bug tracker!).
Decryption of messages that are both signed and encrypted seems to fail
if the signers key is not present in the users keyring. I don't see any
reason why decryption should fail, since it shouldn't have anything to
do with the signer. The message should decrypt, and there should only
be a signature verification error.
I haven't checked to see if this has been reported upstream or not.
I'll try to look into it.
jamie.
[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]
next reply other threads:[~2011-11-04 18:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-04 18:00 Jameson Graef Rollins [this message]
2014-01-23 13:37 ` decryption error for signed+encrypted messages David Bremner
2019-05-06 21:09 ` Daniel Kahn Gillmor
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=87obwrix8s.fsf@servo.finestructure.net \
--to=jrollins@finestructure.net \
--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).