unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Rainer Gemulla <rgemulla@gmx.de>
To: David Bremner <david@tethera.net>, notmuch@notmuchmail.org
Cc: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
Subject: Re: notmuch-show: Verification via epa-verify-region affected by formatting hooks
Date: Tue, 09 Apr 2019 19:50:39 +0200	[thread overview]
Message-ID: <87tvf7xe34.fsf@gemma> (raw)
In-Reply-To: <87imvscwrp.fsf@tethera.net>

[-- Attachment #1: Type: text/plain, Size: 1795 bytes --]

Thanks David! I updated the Wiki accordingly. This issue can be closed from my point of view.

Best,
Rainer

David Bremner <david@tethera.net> writes:

> Rainer Gemulla <rgemulla@gmx.de> writes:
>
>> Hi all,
>>
>> when a message contains an text/plain part that is signed via inline pgp and shown in notmuch-show-mode, verification of that part's signature via epa-mail-verify or epa-verify-region fails. 
>>
>> The reason is that the hooks in notmuch-show-insert-text/plain-hook modify the text (and thus the signature becomes invalid). Calling notmuch-show-pipe-part with "gpg --verify" works as expected and verifies the correctness of the signature.
>>
>> Not sure what to do about this, but I find the current behavior confusing. The notmuch emacstips documentation also (implicitly) states that verification of inline pgp can be done via the epa-* functions. 
>>
>
> That documentation is wiki. That means both that you should take it with
> a grain of salt, and that we welcome updates to it
>
>   https://notmuchmail.org/wikiwriteaccess/
>   
>> One option may be to document this behavior. Another one to add a
>> function like notmuch-crypto-verify-part (which is what I currently
>> do).
>
> I suppose that you could also customize notmuch-show-insert-text/plain-hook
>
>> And/or one may be verify each inline pgp signature part by
>> default (when crypto processing is enabled) and add a "crypto button".
>
> As far as documentation in the wiki there is a FAQ about (non) support
> for inline PGP. I think dkg (in copy) was working on decryption of
> inline PGP, but explicitely not on verifying signatures. You can read a
> summary of his issues with inline PGP signatures at
>
>         https://dkg.fifthhorseman.net/notes/inline-pgp-harmful/

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

      reply	other threads:[~2019-04-09 17:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-04 15:19 notmuch-show: Verification via epa-verify-region affected by formatting hooks Rainer Gemulla
2019-04-05 15:11 ` David Bremner
2019-04-09 17:50   ` Rainer Gemulla [this message]

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=87tvf7xe34.fsf@gemma \
    --to=rgemulla@gmx.de \
    --cc=david@tethera.net \
    --cc=dkg@fifthhorseman.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).