From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: Simon Hirscher <public@simonhirscher.de>
Cc: notmuch <notmuch@notmuchmail.org>
Subject: Re: [BUG] Decryption fails if message was signed with an unknown key
Date: Tue, 24 Sep 2013 19:14:22 -0400 [thread overview]
Message-ID: <52421CCE.6030006@fifthhorseman.net> (raw)
In-Reply-To: <CAEj42wuNziY65Q=9cS7kJquNrmrsd91gp34b4=4xrsoBcYfZnQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 721 bytes --]
On 09/23/2013 07:23 PM, Simon Hirscher wrote:
> Now, in order for you to test that behavior I'm going to send you a
> signed and encrypted message because that should exactly reproduce the
> bug, as long as you don't import my key (id EBACABE5 /
> http://simonhirscher.de/public_key.asc) for signature verification.
message received and tested on debian jessie using notmuch 0.16-1, and i
did not see this misbehavior.
Simon, for future reference, you can also test this sort of thing
yourself by making multiple (phony) gpg homedirectories and notmuch
config files, and setting GNUPGHOME and NOTMUCH_CONFIG environment
variables appropriately. I find this a pretty handy diagnostic approach.
--dkg
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 1027 bytes --]
next prev parent reply other threads:[~2013-09-24 23:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-04 22:01 [BUG] Decryption fails if message was signed with an unknown key Simon Hirscher
2013-09-05 15:03 ` Daniel Kahn Gillmor
2013-09-23 23:23 ` Simon Hirscher
2013-09-24 23:14 ` Daniel Kahn Gillmor [this message]
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=52421CCE.6030006@fifthhorseman.net \
--to=dkg@fifthhorseman.net \
--cc=notmuch@notmuchmail.org \
--cc=public@simonhirscher.de \
/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).