Re: Emacs not finding keys to verify signatures

diff --git a/23/883f11396a22fac131de3ed9bfdb2e465ca11e b/23/883f11396a22fac131de3ed9bfdb2e465ca11e
new file mode 100644 (file)
index 0000000..4acb7e6
--- /dev/null
+++ b/23/883f11396a22fac131de3ed9bfdb2e465ca11e
@@ -0,0 +1,111 @@
+Return-Path: <dbp@dbpmail.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 15FA2431FB6\r
+       for <notmuch@notmuchmail.org>; Sat, 29 Jun 2013 08:24:57 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Amavis-Alert: BAD HEADER SECTION, Improper folded header field made up\r
+       entirely of whitespace (char 20 hex): X-Spam-Report: ...T_ADDRESS@@\r
+       for details.\n \n Content previ[...]\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 tpjZjLiiF28f for <notmuch@notmuchmail.org>;\r
+       Sat, 29 Jun 2013 08:24:47 -0700 (PDT)\r
+Received: from dbpmail.net (dbpmail.net [192.81.216.215])\r
+       (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits))\r
+       (No client certificate requested)\r
+       by olra.theworths.org (Postfix) with ESMTPS id A31B8431FAE\r
+       for <notmuch@notmuchmail.org>; Sat, 29 Jun 2013 08:24:47 -0700 (PDT)\r
+Received: from ip68-230-153-180.ri.ri.cox.net ([68.230.153.180] helo=thinkpad)\r
+       by dbpmail.net with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128)\r
+       (Exim 4.80) (envelope-from <dbp@dbpmail.net>)\r
+       id 1Usx11-0000yZ-Ix; Sat, 29 Jun 2013 15:24:44 +0000\r
+From: Daniel Patterson <dbp@dbpmail.net>\r
+To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>,\r
+       David Bremner <david@tethera.net>\r
+Subject: Re: Emacs not finding keys to verify signatures\r
+In-Reply-To: <51CDA80A.9050700@fifthhorseman.net>\r
+References:\r
+ <87sj07a72g.fsf@thinkpad.i-did-not-set--mail-host-address--so-tickle-me>\r
+       <87sj028ovv.fsf@zancas.localnet> <87ehbmpeg5.fsf@mbp.dbpmail.net>\r
+       <87zjua9sxi.fsf@convex-new.cs.unb.ca>   <51CDA80A.9050700@fifthhorseman.net>\r
+User-Agent: Notmuch/0.15.2 (http://notmuchmail.org) Emacs/24.2.1\r
+       (i686-pc-linux-gnu)\r
+Date: Sat, 29 Jun 2013 11:24:31 -0400\r
+Message-ID:\r
+ <878v1tdjo0.fsf@thinkpad.i-did-not-set--mail-host-address--so-tickle-me>\r
+MIME-Version: 1.0\r
+Content-Type: multipart/signed; boundary="=-=-=";\r
+       micalg=pgp-sha1; protocol="application/pgp-signature"\r
+Cc: 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: Sat, 29 Jun 2013 15:24:57 -0000\r
+\r
+--=-=-=\r
+Content-Type: text/plain\r
+\r
+Daniel Kahn Gillmor <dkg@fifthhorseman.net> writes:\r
+> Daniel: on your remote host, have you tried fetching the relevant keys\r
+> into your gpg keyring?  you don't need to create any secret key material\r
+> on the remote host, just fetch the keys as you normally would any other\r
+> user's public key material; then you'll want to mark your own key as\r
+> "ultimately" trusted on the remote host.\r
+\r
+This works. Thanks a lot!\r
+\r
+> you'll want to maintain this public keyring on that host to be able to\r
+> verify the messages, but you don't need to do anything else with it.\r
+>\r
+> this makes me wonder if the actions that get triggered on those\r
+> "unverified" crypto buttons in the display interface need to be\r
+> customizable to send the commands to a remote gpg as well, instead of\r
+> assuming that they are local.\r
+\r
+Yeah, it would be good if there were a hook to be able to send to remote\r
+gpg... because everything else works so smoothly with simple\r
+wrappers. Even if it were just a matter of setting a custom gpg command\r
+(like gpg-notmuch, which would be a shell script that would send the\r
+calls to the remote gpg).\r
+\r
+With notmuch, I can just override the command itself, because there is\r
+no local meaning... but I obviously don't want to override gpg globally\r
+- only in the context of adding public keys.\r
+\r
+--=-=-=\r
+Content-Type: application/pgp-signature\r
+\r
+-----BEGIN PGP SIGNATURE-----\r
+Version: GnuPG v1.4.11 (GNU/Linux)\r
+\r
+iQIcBAEBAgAGBQJRzvwvAAoJECdH7EipjUrwpU4P/23cHU/B9rDiZUZHs2cg5p6g\r
+uukk4WLNCvwb8rlO8BQ7lMfyl+1KhSCJR6OEItwzzrR99TeLqOVGqvMVl6WqAiqM\r
++L0+JT8wUOZ1ll9fr3hcHjBqkxYvf8zqJ+zVpNb+s97vhqjgExObZXMr5kv/Bffu\r
+d/u2qtfpEc2c0vW/4XKD/RPWNyrLKS4ushsWFMefTSNHxhqmwhZfTNMCdNtCNRtD\r
+OD99I43iMnTzlx2q/73GcT+1LapSOiu4Xny2eLmBb3KQl8t5Mn8BzUavyDdw97YV\r
+/eb11mS/LfUndnVtCxcCYkC0F8YQIibnq+PVLm94U8geGws94VsPlmua5V4/tJJn\r
+7AdPqiIrgDiQ94r+J06vlKX6X6xVuK01/SZrxqtoAJRyTyBElWh87KVYq6zUeVs0\r
+vhw6jN8jZgxG/bJEC+OU8s9mMMKBkkC+ylCf2ODjMLN9KNQPUMU4x22gPFNVB6EH\r
+exkiFBCB4VVjiiD4FtQeWoaf+6parcygeZka0BghlkyfGUwp6xWqHA1P+xaIDjeA\r
+o/T12gSgbEnT5b++J8GhKC58Rtv6nKGliZlepvZSRaZxckhFZwNqqCLrH1m+bEOn\r
+XPhoymks3pqPCvWzBhTIjvfZC7e0i/g93URu7bsQyVHRKTwd6RV9Cjh1T0y3e+IW\r
+69EFFYotAHxMq/Q7iwNg\r
+=jwVp\r
+-----END PGP SIGNATURE-----\r
+--=-=-=--\r