1 Return-Path: <dbp@dbpmail.net>
\r
2 X-Original-To: notmuch@notmuchmail.org
\r
3 Delivered-To: notmuch@notmuchmail.org
\r
4 Received: from localhost (localhost [127.0.0.1])
\r
5 by olra.theworths.org (Postfix) with ESMTP id 15FA2431FB6
\r
6 for <notmuch@notmuchmail.org>; Sat, 29 Jun 2013 08:24:57 -0700 (PDT)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
8 X-Amavis-Alert: BAD HEADER SECTION, Improper folded header field made up
\r
9 entirely of whitespace (char 20 hex): X-Spam-Report: ...T_ADDRESS@@
\r
10 for details.\n \n Content previ[...]
\r
14 X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none]
\r
16 Received: from olra.theworths.org ([127.0.0.1])
\r
17 by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)
\r
18 with ESMTP id tpjZjLiiF28f for <notmuch@notmuchmail.org>;
\r
19 Sat, 29 Jun 2013 08:24:47 -0700 (PDT)
\r
20 Received: from dbpmail.net (dbpmail.net [192.81.216.215])
\r
21 (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits))
\r
22 (No client certificate requested)
\r
23 by olra.theworths.org (Postfix) with ESMTPS id A31B8431FAE
\r
24 for <notmuch@notmuchmail.org>; Sat, 29 Jun 2013 08:24:47 -0700 (PDT)
\r
25 Received: from ip68-230-153-180.ri.ri.cox.net ([68.230.153.180] helo=thinkpad)
\r
26 by dbpmail.net with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128)
\r
27 (Exim 4.80) (envelope-from <dbp@dbpmail.net>)
\r
28 id 1Usx11-0000yZ-Ix; Sat, 29 Jun 2013 15:24:44 +0000
\r
29 From: Daniel Patterson <dbp@dbpmail.net>
\r
30 To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>,
\r
31 David Bremner <david@tethera.net>
\r
32 Subject: Re: Emacs not finding keys to verify signatures
\r
33 In-Reply-To: <51CDA80A.9050700@fifthhorseman.net>
\r
35 <87sj07a72g.fsf@thinkpad.i-did-not-set--mail-host-address--so-tickle-me>
\r
36 <87sj028ovv.fsf@zancas.localnet> <87ehbmpeg5.fsf@mbp.dbpmail.net>
\r
37 <87zjua9sxi.fsf@convex-new.cs.unb.ca> <51CDA80A.9050700@fifthhorseman.net>
\r
38 User-Agent: Notmuch/0.15.2 (http://notmuchmail.org) Emacs/24.2.1
\r
40 Date: Sat, 29 Jun 2013 11:24:31 -0400
\r
42 <878v1tdjo0.fsf@thinkpad.i-did-not-set--mail-host-address--so-tickle-me>
\r
44 Content-Type: multipart/signed; boundary="=-=-=";
\r
45 micalg=pgp-sha1; protocol="application/pgp-signature"
\r
46 Cc: notmuch@notmuchmail.org
\r
47 X-BeenThere: notmuch@notmuchmail.org
\r
48 X-Mailman-Version: 2.1.13
\r
50 List-Id: "Use and development of the notmuch mail system."
\r
51 <notmuch.notmuchmail.org>
\r
52 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
53 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
54 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
55 List-Post: <mailto:notmuch@notmuchmail.org>
\r
56 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
57 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
58 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
59 X-List-Received-Date: Sat, 29 Jun 2013 15:24:57 -0000
\r
62 Content-Type: text/plain
\r
64 Daniel Kahn Gillmor <dkg@fifthhorseman.net> writes:
\r
65 > Daniel: on your remote host, have you tried fetching the relevant keys
\r
66 > into your gpg keyring? you don't need to create any secret key material
\r
67 > on the remote host, just fetch the keys as you normally would any other
\r
68 > user's public key material; then you'll want to mark your own key as
\r
69 > "ultimately" trusted on the remote host.
\r
71 This works. Thanks a lot!
\r
73 > you'll want to maintain this public keyring on that host to be able to
\r
74 > verify the messages, but you don't need to do anything else with it.
\r
76 > this makes me wonder if the actions that get triggered on those
\r
77 > "unverified" crypto buttons in the display interface need to be
\r
78 > customizable to send the commands to a remote gpg as well, instead of
\r
79 > assuming that they are local.
\r
81 Yeah, it would be good if there were a hook to be able to send to remote
\r
82 gpg... because everything else works so smoothly with simple
\r
83 wrappers. Even if it were just a matter of setting a custom gpg command
\r
84 (like gpg-notmuch, which would be a shell script that would send the
\r
85 calls to the remote gpg).
\r
87 With notmuch, I can just override the command itself, because there is
\r
88 no local meaning... but I obviously don't want to override gpg globally
\r
89 - only in the context of adding public keys.
\r
92 Content-Type: application/pgp-signature
\r
94 -----BEGIN PGP SIGNATURE-----
\r
95 Version: GnuPG v1.4.11 (GNU/Linux)
\r
97 iQIcBAEBAgAGBQJRzvwvAAoJECdH7EipjUrwpU4P/23cHU/B9rDiZUZHs2cg5p6g
\r
98 uukk4WLNCvwb8rlO8BQ7lMfyl+1KhSCJR6OEItwzzrR99TeLqOVGqvMVl6WqAiqM
\r
99 +L0+JT8wUOZ1ll9fr3hcHjBqkxYvf8zqJ+zVpNb+s97vhqjgExObZXMr5kv/Bffu
\r
100 d/u2qtfpEc2c0vW/4XKD/RPWNyrLKS4ushsWFMefTSNHxhqmwhZfTNMCdNtCNRtD
\r
101 OD99I43iMnTzlx2q/73GcT+1LapSOiu4Xny2eLmBb3KQl8t5Mn8BzUavyDdw97YV
\r
102 /eb11mS/LfUndnVtCxcCYkC0F8YQIibnq+PVLm94U8geGws94VsPlmua5V4/tJJn
\r
103 7AdPqiIrgDiQ94r+J06vlKX6X6xVuK01/SZrxqtoAJRyTyBElWh87KVYq6zUeVs0
\r
104 vhw6jN8jZgxG/bJEC+OU8s9mMMKBkkC+ylCf2ODjMLN9KNQPUMU4x22gPFNVB6EH
\r
105 exkiFBCB4VVjiiD4FtQeWoaf+6parcygeZka0BghlkyfGUwp6xWqHA1P+xaIDjeA
\r
106 o/T12gSgbEnT5b++J8GhKC58Rtv6nKGliZlepvZSRaZxckhFZwNqqCLrH1m+bEOn
\r
107 XPhoymks3pqPCvWzBhTIjvfZC7e0i/g93URu7bsQyVHRKTwd6RV9Cjh1T0y3e+IW
\r
108 69EFFYotAHxMq/Q7iwNg
\r
110 -----END PGP SIGNATURE-----
\r