1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <pete@petertodd.org>) id 1Z2lYB-0003f9-9j
for bitcoin-development@lists.sourceforge.net;
Wed, 10 Jun 2015 19:20:35 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of petertodd.org
designates 62.13.148.154 as permitted sender)
client-ip=62.13.148.154; envelope-from=pete@petertodd.org;
helo=outmail148154.authsmtp.co.uk;
Received: from outmail148154.authsmtp.co.uk ([62.13.148.154])
by sog-mx-2.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
id 1Z2lYA-0006N4-3w for bitcoin-development@lists.sourceforge.net;
Wed, 10 Jun 2015 19:20:35 +0000
Received: from mail-c235.authsmtp.com (mail-c235.authsmtp.com [62.13.128.235])
by punt15.authsmtp.com (8.14.2/8.14.2/) with ESMTP id t5AJKD3C088435;
Wed, 10 Jun 2015 20:20:13 +0100 (BST)
Received: from savin.petertodd.org (75-119-251-161.dsl.teksavvy.com
[75.119.251.161]) (authenticated bits=128)
by mail.authsmtp.com (8.14.2/8.14.2/) with ESMTP id t5AJK5r3001181
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO);
Wed, 10 Jun 2015 20:20:07 +0100 (BST)
Date: Wed, 10 Jun 2015 15:20:04 -0400
From: Peter Todd <pete@petertodd.org>
To: Andy Schroder <info@AndySchroder.com>
Message-ID: <20150610192004.GB21416@savin.petertodd.org>
References: <1943127.DBnVxmfOIh@1337h4x0r>
<20150610093556.GA11409@amethyst.visucore.com>
<557869F9.8030109@AndySchroder.com> <557883A7.7030906@sky-ip.org>
<55788924.6090008@AndySchroder.com>
<20150610190320.GA1229@savin.petertodd.org>
<55788C02.1010105@AndySchroder.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
protocol="application/pgp-signature"; boundary="2B/JsCI69OhZNC5r"
Content-Disposition: inline
In-Reply-To: <55788C02.1010105@AndySchroder.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Server-Quench: b4e1059d-0fa5-11e5-b396-002590a15da7
X-AuthReport-Spam: If SPAM / abuse - report it at:
http://www.authsmtp.com/abuse
X-AuthRoute: OCd2Yg0TA1ZNQRgX IjsJECJaVQIpKltL GxAVKBZePFsRUQkR
bwdMdwIUEkAaAgsB AmMbWVReUl17WWs7 bA9PbARUfEhLXhtr
VklWR1pVCwQmRRlw fGUbEBpydwRHcH8+ ZEBqXHQVDkAvdEZ4
SxpJFTtXYHphaTUa TRJbfgVJcANIexZF O1F6ACIKLwdSbGoL
NQ4vNDcwO3BTJTpY RgYVKF8UXXNDPyV0 fBcfBz4iM0ofSCh7
NAAnLlpUAFwMKVkt NkE9WUNQPhkVFwJe V11KYmdZIEIdDzYr DBgSWU8FDGo1
X-Authentic-SMTP: 61633532353630.1023:706
X-AuthFastPath: 0 (Was 255)
X-AuthSMTP-Origin: 75.119.251.161/587
X-AuthVirus-Status: No virus detected - but ensure you scan with your own
anti-virus system.
X-Spam-Score: -1.5 (-)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
-0.0 SPF_PASS SPF: sender matches SPF record
X-Headers-End: 1Z2lYA-0006N4-3w
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Is SourceForge still trustworthy enough
to host this list?
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Wed, 10 Jun 2015 19:20:35 -0000
--2B/JsCI69OhZNC5r
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Wed, Jun 10, 2015 at 03:12:02PM -0400, Andy Schroder wrote:
>=20
> Andy Schroder
>=20
> On 06/10/2015 03:03 PM, Peter Todd wrote:
> >
> >>4. Seems like digital signatures are always broken on messages because
> >> the list server slightly modifies them (?), so my e-mail client
> >> doesn't verify them all.
> >What type of digital signatures specifically? What email client?
>=20
> I think they are usually PGP/MIME signatures that are not working
> right. If you'll notice from my e-mail headers:
>=20
> User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thund=
erbird/24.2.0
> X-Enigmail-Version: 1.6
It might be that Thunderbird doesn't properly handle messages with both
signed and unsigned content. I use mutt myself, which handles it just
fine. (the sigs on your emails verify just fine for instance)
--=20
'peter'[:-1]@petertodd.org
0000000000000000134f9a433a4bece258b5035ecda33384f820a60493ca2887
--2B/JsCI69OhZNC5r
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
-----BEGIN PGP SIGNATURE-----
iQGrBAEBCACVBQJVeI3hXhSAAAAAABUAQGJsb2NraGFzaEBiaXRjb2luLm9yZzAw
MDAwMDAwMDAwMDAwMDAxMzRmOWE0MzNhNGJlY2UyNThiNTAzNWVjZGEzMzM4NGY4
MjBhNjA0OTNjYTI4ODcvFIAAAAAAFQARcGthLWFkZHJlc3NAZ251cGcub3JncGV0
ZUBwZXRlcnRvZC5vcmcACgkQJIFAPaXwkftHlwf8DGCeh8bILCbick3vyiT8e4u0
bdj+c62UWvyijbjeK6Ce1wgtTYbrQs85pdT/tzGDguyRdHtKiZhkzBd4DR8bXFiS
NMdZn9zQgyeArt7EQ5plePXiBLmBKtcC4kIbDv8H3jhYrBHkS0qSzUBCvsytVlH/
Su5B1/Dt0X2OeXFK8f/2tSUCtlXb7xTpexA4puyLwXq5HQ5cVJUgwKK4wBRm30fy
hD3lEJlMLeFtYtmvCzdJKnP9c5ksUXzY2VmDspmetA/Jg32FVM29EUVr7ODDoqK8
gkr/y8TsGOdlAIZh7vXLh7Ehqnvot/WOXbylRLD+ALUB49Rtx83qkQC9rInHUw==
=vZn8
-----END PGP SIGNATURE-----
--2B/JsCI69OhZNC5r--
|
