From: Jan Malakhovski <oxij@oxij.org>
To: David Bremner <david@tethera.net>, notmuch@notmuchmail.org
Subject: Re: [PATCH] crypto: gracefully handle gmime errors
Date: Thu, 31 Aug 2017 23:59:05 +0000 [thread overview]
Message-ID: <87y3pz47cm.fsf@oxij.org> (raw)
In-Reply-To: <878thz74qf.fsf@tethera.net>
David Bremner <david@tethera.net> writes:
> Jan Malakhovski <oxij@oxij.org> writes:
>
>>
>> The test suite has such a message already. "signature verification
>> (notmuch CLI)" test fails with a SIGSEGV when built with gmime-2.6.23.
>>
>> T355-smime: Testing S/MIME signature verification and decryption
>> gpgsm: keybox '/tmp/nix-build-notmuch-0.25.drv-0/notmuch-test-8789.qe2sRf/gnupg/pubring.kbx' created
>> PASS emacs delivery of S/MIME signed message
>> PASS emacs delivery of S/MIME encrypted + signed message
>> PASS Signature verification (openssl)
>> FAIL signature verification (notmuch CLI)
>
> Actually now that I try, I can't duplicate this failure on Debian (also
> with gmime-2.6.23). Matt, can you confirm or deny that the failures you
> were having were with SMIME signed messages?
Versions of all dependencies as per diff of `nix-store -q --requisites`
between two builds, if it helps:
--- /proc/self/fd/11 2017-08-31 23:53:53.387411873 +0000
+++ /proc/self/fd/12 2017-08-31 23:53:53.405412185 +0000
@@ -1,10 +1,9 @@
/nix/store/y4ihw837rm0s0ps5f31zi18w7ri1a0y8-glibc-2.25
/nix/store/bcg4yk2kinfd9703m3qlh7gkivkg1kqj-zlib-1.2.11
/nix/store/2hd1rag058ija0ivn3ip4lfjdsnk1l9r-glib-2.52.1
-/nix/store/3ia3cz1hikmfhwgmbyf0j005myh9y7rb-gmime-2.6.23
+/nix/store/8ms9r6qw41rds9f59swiaaypmx07p376-gmime-3.0.1
/nix/store/axldd4qjamb2c1lgi7d6k3s51qyy4610-bash-4.4-p12
/nix/store/ds1qs36gzkzr4z6fvpdchwkhgkwq94p5-gcc-6.4.0-lib
/nix/store/9636ksx6g2yifzx4d3wcfir87s3dzlja-xapian-1.4.4
-/nix/store/g3px2vjcfhaq7f6hdm1xnmbk5ry5qjrv-gnupg-2.1.23
/nix/store/wfq4aip4ljnv0irx0r8b54pihfhz6im9-talloc-2.1.8
-/nix/store/h0lzwh8pmpcdzg7q8xl9bj5lzd9rvf71-notmuch-0.25
+/nix/store/kfwjlk0mqzisc77zxiflbamnrc52mfhq-notmuch-0.25
I wonder why gnupg stops getting referenced with gmime-3.0.1. My guess
is that `./configure` does something very different when compiling with
gmime-3.
Also, I think another message of mine got stuck in premoderation because
it had a biggish attachment with a build log.
Cheers,
Jan
next prev parent reply other threads:[~2017-09-01 0:00 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-31 13:31 [PATCH] crypto: gracefully handle gmime errors Jan Malakhovski
2017-08-31 13:44 ` Jan Malakhovski
2017-09-01 0:10 ` [PATCH] cli: propagate NULL from _mime_node_create, handle it in callers David Bremner
2017-09-01 20:32 ` Jan Malakhovski
2017-08-31 14:22 ` [PATCH] crypto: gracefully handle gmime errors David Bremner
2017-08-31 14:30 ` David Bremner
2017-08-15 17:37 ` bug: notmuch show --decrypt leads to SIGSEGV Matt Armstrong
2017-08-15 18:11 ` David Bremner
2017-08-15 19:10 ` Matt Armstrong
2017-08-15 23:12 ` David Bremner
2017-08-16 16:41 ` Matt Armstrong
2017-08-20 13:43 ` David Bremner
2017-08-31 15:17 ` [PATCH] crypto: gracefully handle gmime errors Jan Malakhovski
2017-08-31 18:33 ` David Bremner
2017-08-31 22:27 ` David Bremner
2017-08-31 23:20 ` Matt Armstrong
2017-08-31 23:59 ` Jan Malakhovski [this message]
2017-11-10 1:05 ` bug: notmuch show --decrypt leads to SIGSEGV David Bremner
2017-08-31 14:34 ` [BUG] gmime-3.0.1 (was: [PATCH] crypto: gracefully handle gmime errors) Jan Malakhovski
2017-09-05 10:54 ` David Bremner
2017-09-05 12:55 ` Jan Malakhovski
2017-09-05 13:38 ` David Bremner
2017-09-05 14:26 ` Jan Malakhovski
2017-09-05 15:26 ` David Bremner
2017-09-05 20:23 ` Jan Malakhovski
2017-09-05 14:04 ` Servilio Afre Puentes
2017-09-05 14:27 ` Jan Malakhovski
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=87y3pz47cm.fsf@oxij.org \
--to=oxij@oxij.org \
--cc=david@tethera.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).