From: Holger Schurig <holgerschurig@gmail.com>
To: notmuch@notmuchmail.org
Subject: Segfault with pkcs7 message
Date: Fri, 3 Nov 2017 10:05:22 +0100 [thread overview]
Message-ID: <CAOpc7mF0VKS9YGrjkfMgMk-Ht70nXDmDCg0yen5Wf6VGN+PKUg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 414 bytes --]
The attached e-mail makes notmuch from git HEAD segfault:
$ notmuch --version
notmuch 0.25.1+161~g1b91884
$ notmuch show --decrypt id:86595dab-d486-536b-fe7a-ae3e1dca1a26@posteo.de
Warning: Crypto engine initialization failure (application/pkcs7-signature).
Segmentation fault
Without the --decrypt I can see the visible text, but I'm unaware on how I
can make the elisp code not send this command line option.
[-- Attachment #2: Type: text/html, Size: 626 bytes --]
next reply other threads:[~2017-11-03 9:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-03 9:05 Holger Schurig [this message]
2017-11-03 9:11 ` Segfault with pkcs7 message Jani Nikula
2017-11-06 1:07 ` 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=CAOpc7mF0VKS9YGrjkfMgMk-Ht70nXDmDCg0yen5Wf6VGN+PKUg@mail.gmail.com \
--to=holgerschurig@gmail.com \
--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).