From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: David Edmondson <dme@dme.org>
Cc: notmuch <notmuch@notmuchmail.org>
Subject: Re: a proposed change to JSON output to report verification of PGP/MIME signatures.
Date: Mon, 15 Nov 2010 11:40:43 -0500 [thread overview]
Message-ID: <4CE1628B.90206@fifthhorseman.net> (raw)
In-Reply-To: <871v6mzxza.fsf@ut.hh.sledj.net>
[-- Attachment #1: Type: text/plain, Size: 955 bytes --]
On 11/15/2010 05:23 AM, David Edmondson wrote:
> i.e. the existence of the multipart/signed wrapper should be
> explicit. In general, all MIME parts should be visible.
thanks, this makes sense to me.
> Changing the JSON output in this way would not materially affect your
> proposal, I believe. There'd be some implicit changes in the output (for
> example, if a signature signs a multipart/mixed part your proposal would
> list it as signing the sub-parts of the multipart/mixed, but with my
> additional changes it should be listed as signing the multipart/mixed
> itself).
this is interesting: under your proposed changes, the "signs" element
would not need to be a list any more. it could just be a single part ID.
I think i like that.
"sigstatus" would still need to be a list, though, since you can have a
signature part that contains multiple signature packets.
Thanks for helping think this through, David.
--dkg
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 900 bytes --]
next prev parent reply other threads:[~2010-11-15 16:41 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 [this message]
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
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=4CE1628B.90206@fifthhorseman.net \
--to=dkg@fifthhorseman.net \
--cc=dme@dme.org \
--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).