Re: [Review] Re: new "crypto" branch providing full PGP/MIME support

diff --git a/ea/4c7ad50d58c38ecf02157db338f9efbdc3e244 b/ea/4c7ad50d58c38ecf02157db338f9efbdc3e244
new file mode 100644 (file)
index 0000000..4953b99
--- /dev/null
+++ b/ea/4c7ad50d58c38ecf02157db338f9efbdc3e244
@@ -0,0 +1,117 @@
+Return-Path: <dkg@fifthhorseman.net>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+       by olra.theworths.org (Postfix) with ESMTP id CDB41431FB6\r
+       for <notmuch@notmuchmail.org>; Mon, 28 Feb 2011 12:08:49 -0800 (PST)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: 0\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none]\r
+       autolearn=disabled\r
+Received: from olra.theworths.org ([127.0.0.1])\r
+       by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)\r
+       with ESMTP id KSmFpvP6SCAO for <notmuch@notmuchmail.org>;\r
+       Mon, 28 Feb 2011 12:08:49 -0800 (PST)\r
+Received: from che.mayfirst.org (che.mayfirst.org [209.234.253.108])\r
+       by olra.theworths.org (Postfix) with ESMTP id 5BC25431FB5\r
+       for <notmuch@notmuchmail.org>; Mon, 28 Feb 2011 12:08:49 -0800 (PST)\r
+Received: from [192.168.23.207] (dsl254-070-154.nyc1.dsl.speakeasy.net\r
+       [216.254.70.154])\r
+       by che.mayfirst.org (Postfix) with ESMTPSA id 960BDF973\r
+       for <notmuch@notmuchmail.org>; Mon, 28 Feb 2011 15:08:46 -0500 (EST)\r
+Message-ID: <4D6C00C7.9000705@fifthhorseman.net>\r
+Date: Mon, 28 Feb 2011 15:08:39 -0500\r
+From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>\r
+User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;\r
+       rv:1.9.2.13) Gecko/20101213 Icedove/3.1.7\r
+MIME-Version: 1.0\r
+To: notmuch <notmuch@notmuchmail.org>\r
+Subject: Re: [Review] Re: new "crypto" branch providing full PGP/MIME support\r
+References: <4CF15D67.1070904@fifthhorseman.net>\r
+       <87aak08fu8.fsf@servo.finestructure.net>\r
+       <87fwsf9mip.fsf@servo.finestructure.net>\r
+       <87tygl29vu.fsf@servo.finestructure.net>\r
+       <87oc5yi9us.fsf@zancas.localnet>\r
+       <87d3mdvjwz.fsf@bookbinder.fernseed.info>\r
+       <87k4gk70ng.fsf@SSpaeth.de>\r
+       <87sjv8i7v6.fsf@irigaray.ross.mayfirst.org>\r
+       <87sjv86mp9.fsf@servo.finestructure.net>\r
+       <4D6BF0AA.3070706@fifthhorseman.net>\r
+       <874o7o6ih5.fsf@servo.finestructure.net>\r
+In-Reply-To: <874o7o6ih5.fsf@servo.finestructure.net>\r
+X-Enigmail-Version: 1.1.2\r
+Content-Type: multipart/signed; micalg=pgp-sha512;\r
+       protocol="application/pgp-signature";\r
+       boundary="------------enig4C161DD2745A51DCB955C40A"\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.13\r
+Precedence: list\r
+Reply-To: notmuch <notmuch@notmuchmail.org>\r
+List-Id: "Use and development of the notmuch mail system."\r
+       <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
+List-Archive: <http://notmuchmail.org/pipermail/notmuch>\r
+List-Post: <mailto:notmuch@notmuchmail.org>\r
+List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
+List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Mon, 28 Feb 2011 20:08:49 -0000\r
+\r
+This is an OpenPGP/MIME signed message (RFC 2440 and 3156)\r
+--------------enig4C161DD2745A51DCB955C40A\r
+Content-Type: text/plain; charset=UTF-8\r
+Content-Transfer-Encoding: quoted-printable\r
+\r
+On 02/28/2011 02:56 PM, Jameson Rollins wrote:\r
+> On Mon, 28 Feb 2011 13:59:54 -0500, Daniel Kahn Gillmor <dkg@fifthhorse=\r
+man.net> wrote:\r
+>> But: what does the "signed" tag mean? i wouldn't want to necessarily\r
+>> conflate these four ideas:\r
+>=20\r
+> These are good points, Daniel.  However, I had actually just been\r
+> thinking of something much simpler, along the lines of just tagging\r
+> "signed" any message with a "multipart/signed" part, and "encrypted" an=\r
+y\r
+> message with a "multipart/encrypted" part.\r
+\r
+this is a fair answer to my questions, not an evasion -- you're\r
+selecting level 0 in both tracks, which is not a bad thing (it's\r
+certainly simpler to get right!)\r
+\r
+The outstanding question in my mind is whether those tags could be\r
+mistaken by a na=C3=AFve user for meaning one of the other concepts.  Is\r
+there a way to name the tags to minimize that kind of confusion?\r
+\r
+       --dkg\r
+\r
+\r
+--------------enig4C161DD2745A51DCB955C40A\r
+Content-Type: application/pgp-signature; name="signature.asc"\r
+Content-Description: OpenPGP digital signature\r
+Content-Disposition: attachment; filename="signature.asc"\r
+\r
+-----BEGIN PGP SIGNATURE-----\r
+Version: GnuPG v1.4.11 (GNU/Linux)\r
+Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/\r
+\r
+iQJ8BAEBCgBmBQJNbADIXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w\r
+ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQwRUU1QkU5NzkyODJEODBCOUY3NTQwRjFD\r
+Q0QyRUQ5NEQyMTczOUU5AAoJEMzS7ZTSFznpo3kQAJ06AD+syC4vJoc0CSXSkf13\r
+RiZ5pAFPHEyV4kRYuPlx30ZdGw9X1/DRaih2dvIj88PM2DoMV3N9TiKjaQOytTxL\r
+vsDDQNUp/9YvnAMgoMF6ddQPsfvwBEaYW256iTDSctQ3rtzX5MWmfrGhln5IOYqF\r
+CAxazaBPkyDgeyj46cRNLp7Z603Z1jzQ8ZVnGNnmjSuyeV0/BCx44cPrcWcnn4Pe\r
+OqEa1byFHbOAvZgdV4qN7dGGWFXshtyRnG9JPASObUyILatv3wESqxZPB2aXIF1h\r
+RLEsP/5soILZoNz/QerR55WriNPPZT4aBQyw20mJNm2corzX0b0t5b91gg6mxtrf\r
+xP3rocdXdZnbJ7hiX1ZnkG23VJLpSthZulFln6A9mZsnacRyT5rcVJCpqxZdKLxD\r
+cSf8Eqw4LoyVCRNBS7b8Uwj02XgQ6YpKCOQWrEcYuDDqoRBN5cb4SOKsQQmUKZ2h\r
+7V1UvOA+DB5L5rriwgWPGhhq+kUkwN0SGa6eVbhQ4OY5eqenjHoCAz9Ad4QOnXkF\r
+8XmBp69kuqvLK7dh5XWHY/RA5C9d2jYxn5wEHHj4tqKj/qCBeiYM5q//L2TW5EYk\r
+Pn0H2VGognOgY4wttjrNrV7LHiRouExCYJT11LqTq/FBPtOfE9fO6RfFSBQ3qfkN\r
+wM/3brd7I9Nv7eUOVsXS\r
+=sdGo\r
+-----END PGP SIGNATURE-----\r
+\r
+--------------enig4C161DD2745A51DCB955C40A--\r