Message-ID: <4D6C00C7.9000705@fifthhorseman.net>
Date: Mon, 28 Feb 2011 15:08:39 -0500
From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.9.2.13) Gecko/20101213 Icedove/3.1.7
MIME-Version: 1.0
To: notmuch <notmuch@notmuchmail.org>
Subject: Re: [Review] Re: new "crypto" branch providing full PGP/MIME support
References: <4CF15D67.1070904@fifthhorseman.net>
	<87aak08fu8.fsf@servo.finestructure.net>
	<87fwsf9mip.fsf@servo.finestructure.net>
	<87tygl29vu.fsf@servo.finestructure.net>
	<87oc5yi9us.fsf@zancas.localnet>
	<87d3mdvjwz.fsf@bookbinder.fernseed.info>
	<87k4gk70ng.fsf@SSpaeth.de>
	<87sjv8i7v6.fsf@irigaray.ross.mayfirst.org>
	<87sjv86mp9.fsf@servo.finestructure.net>
	<4D6BF0AA.3070706@fifthhorseman.net>
	<874o7o6ih5.fsf@servo.finestructure.net>
In-Reply-To: <874o7o6ih5.fsf@servo.finestructure.net>
Content-Type: multipart/signed; micalg=pgp-sha512;
	protocol="application/pgp-signature";
	boundary="------------enig4C161DD2745A51DCB955C40A"
Precedence: list
Reply-To: notmuch <notmuch@notmuchmail.org>

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig4C161DD2745A51DCB955C40A
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On 02/28/2011 02:56 PM, Jameson Rollins wrote:
> On Mon, 28 Feb 2011 13:59:54 -0500, Daniel Kahn Gillmor <dkg@fifthhorse=
man.net> wrote:
>> But: what does the "signed" tag mean? i wouldn't want to necessarily
>> conflate these four ideas:
>=20
> These are good points, Daniel.  However, I had actually just been
> thinking of something much simpler, along the lines of just tagging
> "signed" any message with a "multipart/signed" part, and "encrypted" an=
y
> message with a "multipart/encrypted" part.

this is a fair answer to my questions, not an evasion -- you're
selecting level 0 in both tracks, which is not a bad thing (it's
certainly simpler to get right!)

The outstanding question in my mind is whether those tags could be
mistaken by a na=C3=AFve user for meaning one of the other concepts.  Is
there a way to name the tags to minimize that kind of confusion?

	--dkg


--------------enig4C161DD2745A51DCB955C40A
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.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQJ8BAEBCgBmBQJNbADIXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQwRUU1QkU5NzkyODJEODBCOUY3NTQwRjFD
Q0QyRUQ5NEQyMTczOUU5AAoJEMzS7ZTSFznpo3kQAJ06AD+syC4vJoc0CSXSkf13
RiZ5pAFPHEyV4kRYuPlx30ZdGw9X1/DRaih2dvIj88PM2DoMV3N9TiKjaQOytTxL
vsDDQNUp/9YvnAMgoMF6ddQPsfvwBEaYW256iTDSctQ3rtzX5MWmfrGhln5IOYqF
CAxazaBPkyDgeyj46cRNLp7Z603Z1jzQ8ZVnGNnmjSuyeV0/BCx44cPrcWcnn4Pe
OqEa1byFHbOAvZgdV4qN7dGGWFXshtyRnG9JPASObUyILatv3wESqxZPB2aXIF1h
RLEsP/5soILZoNz/QerR55WriNPPZT4aBQyw20mJNm2corzX0b0t5b91gg6mxtrf
xP3rocdXdZnbJ7hiX1ZnkG23VJLpSthZulFln6A9mZsnacRyT5rcVJCpqxZdKLxD
cSf8Eqw4LoyVCRNBS7b8Uwj02XgQ6YpKCOQWrEcYuDDqoRBN5cb4SOKsQQmUKZ2h
7V1UvOA+DB5L5rriwgWPGhhq+kUkwN0SGa6eVbhQ4OY5eqenjHoCAz9Ad4QOnXkF
8XmBp69kuqvLK7dh5XWHY/RA5C9d2jYxn5wEHHj4tqKj/qCBeiYM5q//L2TW5EYk
Pn0H2VGognOgY4wttjrNrV7LHiRouExCYJT11LqTq/FBPtOfE9fO6RfFSBQ3qfkN
wM/3brd7I9Nv7eUOVsXS
=sdGo
-----END PGP SIGNATURE-----

--------------enig4C161DD2745A51DCB955C40A--