Message-ID: <4CE2EECE.8060000@fifthhorseman.net>
Date: Tue, 16 Nov 2010 15:51:26 -0500
From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.9.2.9) Gecko/20100918 Icedove/3.1.4
MIME-Version: 1.0
To: notmuch <notmuch@notmuchmail.org>
Subject: Re: a proposed change to JSON output to report verification of
	PGP/MIME signatures.
References: <4CDE4486.2050101@fifthhorseman.net>
	<87hbfhdpa6.fsf@yoom.home.cworth.org>
	<87wrod9gh8.fsf@servo.finestructure.net>
	<4CE2E819.1070808@fifthhorseman.net>
	<87sjz19ext.fsf@servo.finestructure.net>
In-Reply-To: <87sjz19ext.fsf@servo.finestructure.net>
OpenPGP: id=D21739E9
Content-Type: multipart/signed; micalg=pgp-sha512;
	protocol="application/pgp-signature";
	boundary="------------enig3BB0C14B825463AF1AC7A227"
Precedence: list
Reply-To: notmuch <notmuch@notmuchmail.org>

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig3BB0C14B825463AF1AC7A227
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On 11/16/2010 03:44 PM, Jameson Rollins wrote:
> Aren't clients going to have to interpret/display the output regardless=

> of it's been verified or not?  It seems to me that understanding how to=

> display the verified output is really not that much more difficult than=

> understanding how to display the unverified output.

With json (and similar formats), it's easy to write a parser that says
"i know what to do with data member $foo -- give me that one".  This
lets you remain in blissful ignorance of data members $bar and $baz.

and if your backend suddenly starts throwing $qux at you as well, you
can just ignore it too, until you find you want to make use of it.

I imagine that someone writing a frontend would want to start with
things like message display, and not bother with fancier bits (such as
signature verification) until later.

frontends that know that their backend is somehow resource constrained
might also want to indicate to the user that a message claims to be
signed but not verify the signature unless the user asks for it.  (i
wish my current MUA had that feature, actually -- some messages i get
are signed but i don't personally need to verify them on every reload
(or even ever), depending on their content, but my MUA always makes me
wait for the verification process to happen.

To be clear -- i think that signature verification should be the default
situation for MUAs that are capable of doing it, but i don't think that
translates into --verify being on by default in
/usr/bin/notmuch.

	--dkg


--------------enig3BB0C14B825463AF1AC7A227
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBCgAGBQJM4u7OAAoJEMzS7ZTSFznpwf4P/1DPv/CrXvZxRikBXUcfy8Mg
HtC27KJWHERvz71TeyOCgXmPgMKqOy/46iyvHvFJ3PRbiB63IOyxBzqtgmuyu35V
BBYJ+4sslmd0kVfKDBi6+uzjuLXTIxkuPlnNLtFxCONbxqJBV7ym7CJm2DTASwP/
OD3VJ68kdC6uaZn6mCVAmlkZSXbJ0fnI8EWBB0WBBwyPzY4ilCH7cy0FMJIp/LDs
0h4x6/wwcAUH8b6TgVp0OfH4iHi1QlzhZ9Dy7LD39rfHTu4rElTOTgEbv36yYsez
DrPwcBuWI7ahakqfmVPTnG3tjnmJ7he+CAtTL6AYSniNvnasnlhjK2pCPRllBqLI
Z86wY7kKIvk0CyOJhy4QxpfBgcOu0F44Dt7peNT4uBqXTUVZhCqTgGvUH9tmShHW
SO31pHHqDZPgK0PGfa5JLzYqubUketZLF01p1QM+7eohFJxSgz7J8vLfh/kLgUdV
7Q67Sp7jAnZ2l4c05UHsohVNwrVMKhZrPyIa/BVfQ5UrUlgYcsVO1TqP5rVUsJGq
oQ2fIyUVBm6WhOHlaNgVZvFcn5dZNksogtT1uf7OT8TIb/EPrZEsC9MvYtO12ZsU
E3+OX962EDJ+EADH3um4zcfFj57CJetbNIw96wZfpJVKiyqBmkQxY3XcwZn337ri
CkgpSH54cl7dWhizkTKi
=7uq2
-----END PGP SIGNATURE-----

--------------enig3BB0C14B825463AF1AC7A227--