From: Jameson Rollins <jrollins@finestructure.net>
To: Carl Worth <cworth@cworth.org>,
Daniel Kahn Gillmor <dkg@fifthhorseman.net>,
notmuch <notmuch@notmuchmail.org>
Subject: Re: a proposed change to JSON output to report verification of PGP/MIME signatures.
Date: Tue, 16 Nov 2010 15:10:59 -0500 [thread overview]
Message-ID: <87wrod9gh8.fsf@servo.finestructure.net> (raw)
In-Reply-To: <87hbfhdpa6.fsf@yoom.home.cworth.org>
[-- Attachment #1: Type: text/plain, Size: 840 bytes --]
On Tue, 16 Nov 2010 11:47:13 -0800, Carl Worth <cworth@cworth.org> wrote:
> The only other piece I think I'd like to see is actually making the
> content of the signature pieces available in the json output. Then, a
> client could do its own verification.
>
> Then if we had that would we not want to add the --verify support into
> notmuch? (My guess is that we still would want it.)
Hey, Carl. I think your suggestion to include the signatures in the
output is a reasonable. However, (I could be misunderstanding your
suggestion but) I really think the Right thing is for notmuch to do the
verification itself. I would almost say that --verify should be the
default, with a --no-verify option. It will make things much easier for
all the UIs if notmuch handles the verification and just outputs the
result.
jamie.
[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]
next prev parent reply other threads:[~2010-11-16 20:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-13 7:55 a proposed change to JSON output to report verification of PGP/MIME signatures Daniel Kahn Gillmor
2010-11-13 11:40 ` David Bremner
2010-11-13 16:00 ` Daniel Kahn Gillmor
2010-11-15 10:23 ` David Edmondson
2010-11-15 16:40 ` Daniel Kahn Gillmor
2010-11-16 19:47 ` Carl Worth
2010-11-16 20:06 ` Daniel Kahn Gillmor
2010-11-24 1:08 ` Daniel Kahn Gillmor
2010-11-16 20:10 ` Jameson Rollins [this message]
2010-11-16 20:22 ` Daniel Kahn Gillmor
2010-11-16 20:44 ` Jameson Rollins
2010-11-16 20:51 ` Daniel Kahn Gillmor
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=87wrod9gh8.fsf@servo.finestructure.net \
--to=jrollins@finestructure.net \
--cc=cworth@cworth.org \
--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).