From: Jameson Rollins <jrollins@finestructure.net>
To: David Bremner <bremner@unb.ca>, notmuch <notmuch@notmuchmail.org>
Subject: Re: new "crypto" branch providing full PGP/MIME support
Date: Fri, 04 Feb 2011 09:24:23 -0800 [thread overview]
Message-ID: <87tygjiugo.fsf@servo.finestructure.net> (raw)
In-Reply-To: <87zkqcugvt.fsf@zancas.localnet>
[-- Attachment #1: Type: text/plain, Size: 1028 bytes --]
On Fri, 04 Feb 2011 08:24:38 -0400, David Bremner <bremner@unb.ca> wrote:
> On Wed, 02 Feb 2011 17:18:45 -0800, Jameson Rollins <jrollins@finestructure.net> wrote:
> > Hi, all. I have pushed a new branch called "crypto" to my notmuch
> > repository [0]. This branch provides full support for PGP/MIME signed
> > and encrypted messages, including emacs UI support. It has been applied
> > on top of cworth's current master (21e97c50). It includes the
> > following:
> >
>
> For a signed and encrypted message, if the signing key can't be found,
> one just gets:
>
> [ multipart/encrypted: decryption error ]
>
> which is a bit mystifying. At least gpg on the command line will
> decrypt the message and print a warning about the signature.
So I need to look at this closer, but I think this is a GMime problem.
That error message is generated when the GMime decryption code returns
NULL for the decrypted part. I'll try to make a test case for this, and
file a bug with GMime upstream.
jamie.
[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]
next prev parent reply other threads:[~2011-02-04 17:24 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-27 19:35 PGP/MIME signature verification Daniel Kahn Gillmor
2010-11-27 21:24 ` Jameson Rollins
2010-12-13 22:02 ` David Bremner
2010-12-13 22:11 ` Daniel Kahn Gillmor
2010-12-13 22:10 ` David Bremner
2010-12-13 22:14 ` Daniel Kahn Gillmor
2010-12-20 18:22 ` Jameson Rollins
2010-12-21 9:51 ` Sebastian Spaeth
2010-12-21 15:36 ` Daniel Kahn Gillmor
2010-12-22 14:38 ` Sebastian Spaeth
2010-12-22 19:11 ` Daniel Kahn Gillmor
2011-01-27 1:13 ` Jameson Rollins
2011-02-03 1:18 ` new "crypto" branch providing full PGP/MIME support Jameson Rollins
2011-02-03 16:25 ` micah anderson
2011-02-03 19:52 ` Daniel Kahn Gillmor
2011-02-03 20:34 ` Jameson Rollins
2011-02-03 21:03 ` always encrypting messages to self [was: Re: new "crypto" branch providing full PGP/MIME support] Daniel Kahn Gillmor
2011-02-04 13:04 ` Sebastian Spaeth
2011-02-04 17:30 ` Jameson Rollins
2011-02-04 16:59 ` new "crypto" branch providing full PGP/MIME support micah anderson
2011-02-04 17:30 ` Daniel Kahn Gillmor
2011-02-03 17:48 ` Daniel Kahn Gillmor
2011-02-03 20:42 ` Darren McGuicken
2011-02-03 21:02 ` Jameson Rollins
2011-02-04 12:09 ` Darren McGuicken
2011-02-04 17:32 ` Jameson Rollins
2011-02-05 14:50 ` Darren McGuicken
2011-02-04 21:07 ` Jameson Rollins
2011-04-25 22:35 ` Jameson Graef Rollins
2011-02-04 12:24 ` David Bremner
2011-02-04 17:24 ` Jameson Rollins [this message]
2011-02-04 17:12 ` David Bremner
2011-02-04 18:10 ` Jameson Rollins
2011-02-27 0:45 ` [Review] " David Bremner
2011-02-27 10:41 ` Darren McGuicken
2011-02-28 13:24 ` Sebastian Spaeth
2011-02-28 13:52 ` Ross Glover
2011-02-28 18:25 ` Jameson Rollins
2011-02-28 18:59 ` Daniel Kahn Gillmor
2011-02-28 19:56 ` Jameson Rollins
2011-02-28 20:08 ` Daniel Kahn Gillmor
2011-03-01 2:49 ` Jameson Rollins
2011-03-01 3:16 ` Rob Browning
2011-03-01 3:31 ` Jameson Rollins
2011-03-05 8:26 ` signed/encrypted tagging in crypto branch [was: Re: [Review] Re: new "crypto" branch providing full PGP/MIME support] Jameson Rollins
2011-03-06 19:15 ` signed/encrypted tagging in crypto branch Jameson Rollins
2011-04-14 7:48 ` Florian Friesdorf
2011-04-16 15:27 ` Pieter Praet
2011-03-01 19:32 ` [Review] Re: new "crypto" branch providing full PGP/MIME support Simon Fondrie-Teitler
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=87tygjiugo.fsf@servo.finestructure.net \
--to=jrollins@finestructure.net \
--cc=bremner@unb.ca \
--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).