Re: Emacs: Crypto: How to get automatic encryption?

diff --git a/bc/6e63b013ae5c80aee0be68b3a73f88df40ad8e b/bc/6e63b013ae5c80aee0be68b3a73f88df40ad8e
new file mode 100644 (file)
index 0000000..6da365f
--- /dev/null
+++ b/bc/6e63b013ae5c80aee0be68b3a73f88df40ad8e
@@ -0,0 +1,140 @@
+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 ECBB2429E36\r
+       for <notmuch@notmuchmail.org>; Wed, 25 Jan 2012 11:09:39 -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 RETEvMc1flE3 for <notmuch@notmuchmail.org>;\r
+       Wed, 25 Jan 2012 11:09:39 -0800 (PST)\r
+Received: from che.mayfirst.org (che.mayfirst.org [209.234.253.108])\r
+       by olra.theworths.org (Postfix) with ESMTP id 4010C431FBC\r
+       for <notmuch@notmuchmail.org>; Wed, 25 Jan 2012 11:09:39 -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 B899FF970;\r
+       Wed, 25 Jan 2012 14:09:33 -0500 (EST)\r
+Message-ID: <4F205368.4020402@fifthhorseman.net>\r
+Date: Wed, 25 Jan 2012 14:09:28 -0500\r
+From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>\r
+User-Agent: Mozilla/5.0 (X11; Linux i686; rv:8.0) Gecko/20120104 Icedove/8.0\r
+MIME-Version: 1.0\r
+To: Jameson Graef Rollins <jrollins@finestructure.net>\r
+Subject: Re: Emacs: Crypto: How to get automatic encryption?\r
+References: <87pqejj5nl.fsf@marcos.anarcat.ath.cx>\r
+       <cunfwfer8i0.fsf@hotblack-desiato.hh.sledj.net>\r
+       <87ehuo7pjr.fsf@algae.riseup.net>\r
+       <87ehuoljzs.fsf@servo.finestructure.net>\r
+       <cunvco0nvwa.fsf@hotblack-desiato.hh.sledj.net>\r
+       <87liow6slg.fsf@servo.finestructure.net>\r
+       <cund3a8nkwl.fsf@hotblack-desiato.hh.sledj.net>\r
+       <878vkv7k2q.fsf@servo.finestructure.net>\r
+In-Reply-To: <878vkv7k2q.fsf@servo.finestructure.net>\r
+X-Enigmail-Version: 1.3.4\r
+Content-Type: multipart/signed; micalg=pgp-sha512;\r
+       protocol="application/pgp-signature";\r
+       boundary="------------enigA0474EB29AD29C958F179AF8"\r
+Cc: Notmuch Mail <notmuch@notmuchmail.org>\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.13\r
+Precedence: list\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: Wed, 25 Jan 2012 19:09:40 -0000\r
+\r
+This is an OpenPGP/MIME signed message (RFC 2440 and 3156)\r
+--------------enigA0474EB29AD29C958F179AF8\r
+Content-Type: text/plain; charset=UTF-8\r
+Content-Transfer-Encoding: quoted-printable\r
+\r
+On 01/25/2012 12:45 PM, Jameson Graef Rollins wrote:\r
+> Here's a behavior that I think would be reasonable:\r
+>=20\r
+>  * notmuch reply outputs JSON encrypted flag\r
+>=20\r
+>  * emacs does a quick check to see if the needed key is available\r
+>=20\r
+>  * if key not available: give a nice mini-buffer prompt, something like=\r
+:\r
+> =20\r
+>     'encryption key for "Foo Bar <foo@bar.com>" not found.  Retrieve?'\r
+>=20\r
+>    * if response is yes: call gpg to retrieve the key\r
+>=20\r
+>  * if key available: add encrypt flag\r
+>=20\r
+>    else: I feel like this should abort, but maybe there's something to\r
+>          be done here.  Allow reply but don't quote the original?\r
+\r
+I note from observing my own correspondence practices that there are\r
+some other heuristics that might be reasonable, if we're willing to be\r
+more sophisticated here too.\r
+\r
+For example:\r
+\r
+ * if the entire encrypted message body was signed by key X (which we\r
+either have or fetch), and\r
+ * X has a User ID which matches the address to which we're replying, and=\r
+\r
+ * we don't have a technically-valid matching User ID for the e-mail\r
+address (so we wouldn't normally want to encrypt mail to key X),\r
+\r
+then\r
+\r
+ we could offer (or default) to encrypt the reply to that key anyway, on\r
+the grounds that the keyholder in question knew the contents of the\r
+original message anyway.\r
+\r
+Some visual indication of being in this corner-case state would be nice,\r
+of course.\r
+\r
+While i'm dreaming, I'd also love to be able to get some statistics\r
+about how many messages in a given thread have this kind\r
+encryption/signing response.  It would be interesting for some sort of\r
+measurement of e-mail+keyholding continuity, which would be useful in a\r
+more generalized contacts+crypto manager.\r
+\r
+       --dkg\r
+\r
+\r
+--------------enigA0474EB29AD29C958F179AF8\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
+iQJ8BAEBCgBmBQJPIFNoXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w\r
+ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQwRUU1QkU5NzkyODJEODBCOUY3NTQwRjFD\r
+Q0QyRUQ5NEQyMTczOUU5AAoJEMzS7ZTSFznpLKoQAKDWSK5n/2YIkTtCVx5rNRWJ\r
+TW6H4TZTICVNlUKuI6wEPo6BEm1olMmd1yiSivdsHVso8MZs/OrXIdWv0M/4XRnh\r
+kVZfmFBjojIQz1eVurMtkfMXflpq1sB8a39iFSDjlbhAx5RFWt1HmUTfrv7vMXkc\r
+kHE9HJGntz5f7krDCK4oBps3bENRqJ/bj+kaxaRvi17QYOiJXUHe2rPkhl1gxIgF\r
++B6zT5FdsIRJodlCzDs8EipztF8ZPPwHTxNUyQTnnOt2mkNsIghRUOMcsK686OSi\r
+uIWZmIEYfvJT0U+v2XMVrjw/Tk7WDxmJdjIKYXuH//I3XD8K+JhSykv8mHc3ror4\r
+9xI+8S2brPQaifQlH3B7dG9TdknGvzVvTjqzOte+BwY5wJ59OgFw1XwYaHuSYZ66\r
+/mNBuTs+ce3pRZnZeBfNP7AKDup0C5sLc8BCsiWhWTcMF+I7zgXIU7ilZre7lKnI\r
+CJ2zv/+2rqN+Fx+uSIYJjDjIkYLZyeBp6gruWfUSrYIldxe51UAEqDtf+BSdsxSp\r
+QpVfU8e2oBRM/a02uA0MEQhbzzT59M/a+Yu8Zo4YyYDagie7LzMPfOBRA49v4Z+g\r
+qBAn610Kc5gOItVvXDyaasFRJ+HhSkDmMnKD7EPnVh5M5YBVlA/bcVfy9dmz5YYk\r
+8D5dL7Udv/Tt1fBQDYSW\r
+=MH2G\r
+-----END PGP SIGNATURE-----\r
+\r
+--------------enigA0474EB29AD29C958F179AF8--\r