From: David Bremner <david@tethera.net>
To: Vagrant Cascadian <vagrant@debian.org>, 755544@bugs.debian.org
Cc: notmuch@notmuchmail.org
Subject: Re: Bug#755544: notmuch-emacs: doesn't check gpg/pgp signatures by default
Date: Mon, 21 Jul 2014 20:16:34 -0300 [thread overview]
Message-ID: <87silucnfx.fsf@maritornes.cs.unb.ca> (raw)
In-Reply-To: <20140721223426.GA5250@siren>
Vagrant Cascadian <vagrant@debian.org> writes:
> Package: notmuch-emacs
> Version: 0.18.1-1
> Severity: important
>
> Thanks for notmuch-emacs, it's great!
>
> I did notice that it doesn't appear to check weather gpg/pgp signatures are
> valid by default.
>
> When I created a signed message to myself, made a copy of it, and then manually
> edited the text within without changing the signature...
>
> But notmuch-emacs doesn't distinguish between the valid signature
:
>
> Subject: valid gpg sig
> To: vagrant@localhost
> Date: Mon, 21 Jul 2014 15:03:45 -0700
>
> [ multipart/signed ]
> [ text/plain ]
> this should be a VALID gpg signature.
> [ signature.asc: application/pgp-signature ]
>
> And the edited text, with an invalid signature:
>
> Subject: invalid gpg sig
> To: vagrant@localhost
> Date: Mon, 21 Jul 2014 15:03:45 -0700
>
> [ multipart/signed ]
> [ text/plain ]
> this should be an INVALID gpg signature.
> [ signature.asc: application/pgp-signature ]
Hi Vagrant;
Thanks for the bug report. It seems that most of the developers
have customized the emacs variable
notmuch-crypto-process-mime to t
For the moment I suggest that as a workaround, and we'll see about
fixing the UI bug upstream.
notmuch folks: it seems that in vagrant's message, and several others I
checked, it notmuch-crypto-process-mime==nil, then no signature button
is created at all.
next parent reply other threads:[~2014-07-21 23:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20140721223426.GA5250@siren>
2014-07-21 23:16 ` David Bremner [this message]
2014-07-22 1:03 ` Bug#755544: notmuch-emacs: doesn't check gpg/pgp signatures by default Jameson Graef Rollins
2014-07-22 4:30 ` Daniel Kahn Gillmor
2014-07-22 4:39 ` Daniel Kahn Gillmor
2014-07-22 9:44 ` David Bremner
2016-02-08 17:46 ` David Edmondson
2017-07-16 12:45 ` 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=87silucnfx.fsf@maritornes.cs.unb.ca \
--to=david@tethera.net \
--cc=755544@bugs.debian.org \
--cc=notmuch@notmuchmail.org \
--cc=vagrant@debian.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).