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: Sat, 20 Jun 2020 12:45:17 -0300 [thread overview]
Message-ID: <87v9jlspv6.fsf@tethera.net> (raw)
In-Reply-To: <87wo45tfg6.fsf@tethera.net>
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
Looking at the sigstatus output, I think it is just a transcription of
what gmime returns.
"encstatus": [
{
"status": "good"
}
],
"sigstatus": [
{
"status": "error",
"keyid": "6D92612D94E46381",
"errors": {
"key-missing": true
}
}
],
I did notice that node->decrypt_success ends up being true, so it
suggests maybe bad reporting by gmime-on-fedora.
next prev parent reply other threads:[~2020-06-20 15:45 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 [this message]
2020-06-28 11:33 ` David Bremner
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=87v9jlspv6.fsf@tethera.net \
--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).