From: David Bremner <david@tethera.net>
To: "Tomi Ollila" <tomi.ollila@iki.fi>,
"Dan Čermák" <dan.cermak@posteo.net>,
notmuch@notmuchmail.org
Cc: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
Subject: Re: crypto test failures on Fedora and OpenSUSE
Date: Sun, 28 Jun 2020 08:33:42 -0300 [thread overview]
Message-ID: <87ftafo25l.fsf@zancas> (raw)
In-Reply-To: <87v9jlspv6.fsf@tethera.net>
David Bremner <david@tethera.net> writes:
> I poked at this a bit more in gdb. I don't really know the code well,
> but it seems like whatever is happening is happening inside gmime. On
> the other hand both Fedora32 and my current Debian testing are running
> libgmime 3.2.7 and gpgme 1.13
>
I dug a bit further down, and this is what is returned from gpgme
(line 345 in g_mime_gpgme_get_signatures)
sig = {next = 0x0,
summary = GPGME_SIGSUM_KEY_MISSING,
fpr = 0x4ac480 "5AEAB11F5E33DCE875DDB75B6D92612D94E46381", status = 9,
notations = 0x0, timestamp = 1559167762, exp_timestamp = 0, wrong_key_usage = 0,
pka_trust = 0, chain_model = 0, is_de_vs = 0, _unused = 0,
validity = GPGME_VALIDITY_UNKNOWN, validity_reason = 0,
pubkey_algo = GPGME_PK_RSA, hash_algo = GPGME_MD_SHA256, pka_address = 0x0,
key = 0x0}
At this point I'm leaning towards declaring it a gpgme problem in
fedora32, and suggesting that relevant distros mark the test broken. I
am of course open to more informed opinions.
d
next prev parent reply other threads:[~2020-06-28 11:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-24 22:03 Feature freeze for notmuch 0.30: June 1 David Bremner
2020-06-02 0:59 ` David Bremner
2020-06-16 12:05 ` David Bremner
2020-06-17 9:18 ` Dan Čermák
2020-06-17 11:53 ` Tomi Ollila
2020-06-17 12:49 ` Tomi Ollila
2020-06-17 23:55 ` crypto test failures on Fedora and OpenSUSE David Bremner
2020-06-20 15:45 ` David Bremner
2020-06-28 11:33 ` David Bremner [this message]
2020-07-02 5:06 ` Daniel Kahn Gillmor
2020-07-02 8:28 ` Dan Čermák
2020-07-02 18:00 ` [PATCH 1/2] configure: can gpgme can verify signatures when decrypting with a session key? Daniel Kahn Gillmor
2020-07-02 18:00 ` [PATCH 2/2] tests: mark sig verification known-broken with session keys on buggy gpgme Daniel Kahn Gillmor
2020-07-03 1:13 ` [PATCH 1/2] configure: can gpgme can verify signatures when decrypting with a session key? David Bremner
2020-07-03 11:35 ` David Bremner
2020-07-03 11:15 ` Feature freeze for notmuch 0.30: June 1 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=87ftafo25l.fsf@zancas \
--to=david@tethera.net \
--cc=dan.cermak@posteo.net \
--cc=dkg@fifthhorseman.net \
--cc=notmuch@notmuchmail.org \
--cc=tomi.ollila@iki.fi \
/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).