unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: Notmuch Mail <notmuch@notmuchmail.org>
Subject: Re: [PATCH v2] configure: Ensure that GMime can extract session keys
Date: Sun, 19 May 2019 23:13:23 -0400	[thread overview]
Message-ID: <87h89pbyy4.fsf@fifthhorseman.net> (raw)
In-Reply-To: <20190506201655.16276-1-dkg@fifthhorseman.net>

[-- Attachment #1: Type: text/plain, Size: 805 bytes --]

On Mon 2019-05-06 16:16:55 -0400, Daniel Kahn Gillmor wrote:
> GMime 3.0 and higher can extract session keys, but it will *not*
> extract session keys if it was built with --disable-crypto, or if it
> was built against GPGME version < 1.8.0.
>
> Notmuch currently expects to be able to extract session keys, and
> tests will fail if it is not possible, so we ensure that this is the
> case during ./configure time.

It would be great to see this patch merged -- it sets up a
./configure-time test to ensure that notmuch can indeed deal with
session keys correctly, which is necessary for the test suite to pass
(and for notmuch to offer sensible decryption and cleartext-indexing
options.

If there's some reason to not merge it, please let me know.  All of its
dependencies have been merged.

     --dkg

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

  parent reply	other threads:[~2019-05-20  3:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-06 19:48 [PATCH] configure: Ensure that GMime can extract session keys Daniel Kahn Gillmor
2019-05-06 20:16 ` [PATCH v2] " Daniel Kahn Gillmor
2019-05-06 20:19   ` Daniel Kahn Gillmor
2019-05-20  3:13   ` Daniel Kahn Gillmor [this message]
2019-05-20 19:46   ` David Bremner
2019-05-20 21:00     ` 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=87h89pbyy4.fsf@fifthhorseman.net \
    --to=dkg@fifthhorseman.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).