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
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <benjamin.l.cordes@gmail.com>) id 1Vxzwo-0006mo-EI
for bitcoin-development@lists.sourceforge.net;
Tue, 31 Dec 2013 14:05:30 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.219.51 as permitted sender)
client-ip=209.85.219.51;
envelope-from=benjamin.l.cordes@gmail.com;
helo=mail-oa0-f51.google.com;
Received: from mail-oa0-f51.google.com ([209.85.219.51])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Vxzwn-00068n-EJ
for bitcoin-development@lists.sourceforge.net;
Tue, 31 Dec 2013 14:05:30 +0000
Received: by mail-oa0-f51.google.com with SMTP id i7so13057288oag.38
for <bitcoin-development@lists.sourceforge.net>;
Tue, 31 Dec 2013 06:05:24 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.182.49.166 with SMTP id v6mr48360235obn.13.1388498723999;
Tue, 31 Dec 2013 06:05:23 -0800 (PST)
Received: by 10.182.233.13 with HTTP; Tue, 31 Dec 2013 06:05:23 -0800 (PST)
In-Reply-To: <CAAS2fgTmWRMxYweu3sNn_X7grgjUqTQujM-DbZRxG_YMZnD=7g@mail.gmail.com>
References: <52A3C8A5.7010606@gmail.com>
<1795f3067ba3fcdd0caf978cc59ff024.squirrel@fruiteater.riseup.net>
<52A435EA.7090405@gmail.com> <201312081237.24473.luke@dashjr.org>
<CANAnSg2OrmQAcZ+cZdtQeADicH3U29QOgYPfP1AQhOMP6+P1wg@mail.gmail.com>
<CAAS2fgR0khyJxmz9c2Oc87hOFgiNuiPJuaeugGajdo_EcKEW9w@mail.gmail.com>
<20131212205106.GA4572@netbook.cypherspace.org>
<CANAnSg3nPhrk2k=yDKf39AuBQnSuTWJbgANdMhGe=soiOy0NTw@mail.gmail.com>
<CAAS2fgTmWRMxYweu3sNn_X7grgjUqTQujM-DbZRxG_YMZnD=7g@mail.gmail.com>
Date: Tue, 31 Dec 2013 15:05:23 +0100
Message-ID: <CAOoPuRYO_Bi41b1VzcXbMeWWSbaXD3u1oooxM3mYrYkmWJLLKQ@mail.gmail.com>
From: Benjamin Cordes <benjamin.l.cordes@gmail.com>
To: Gregory Maxwell <gmaxwell@gmail.com>
Content-Type: multipart/alternative; boundary=047d7b5d2ea437136304eed50d03
X-Spam-Score: -0.6 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked.
See
http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block
for more information. [URIs: doubleclick.net]
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(benjamin.l.cordes[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1Vxzwn-00068n-EJ
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Dedicated server for bitcoin.org,
your thoughts?
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: Tue, 31 Dec 2013 14:05:30 -0000
--047d7b5d2ea437136304eed50d03
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Interesting. I think the original BitDNS discussion was more interesting
that what currently is happening with namecoin, see
https://bitcointalk.org/index.php?topic=3D1790.0
Satoshi said there: "1) IP records don't need to be in the chain, just do
registrar function not DNS. And CA problem solved, neat."
Besides, ICANN is currently selling out the global public namespace - not
that anybody really cares about such measly topics as the ownership of
global namespaces. And so some guy on the Cayman Islands is now the largest
holder of TLD's.
On Tue, Dec 31, 2013 at 2:48 PM, Gregory Maxwell <gmaxwell@gmail.com> wrote=
:
> On Tue, Dec 31, 2013 at 5:39 AM, Drak <drak@zikula.org> wrote:
> > The NSA has the ability, right now to change every download of
> bitcoin-qt,
> > on the fly and the only cure is encryption.
>
> Please cut it out with the snake oil pedaling. This is really over the
> top. You're invoking the NSA as the threat here? Okay. The NSA can
> trivially compromise an HTTPS download site: even ignoring the CA
> insecurity, and government run CAs certificate authorities issue CA
> certs to random governments and corporations for dataloss prevention
> purposes. Not to mention unparalleled access to exploits.
>
> The downloads are protected by something far stronger than SSL
> already, which might even have a chance against the NSA. Actual
> signatures of the downloads with offline keys.
>
> I'm all pro-SSL and all that, but you are=97 piece by piece=97 really
> convincing me that it produces an entirely false sense of security
> which is entirely unjustified.
>
>
> -------------------------------------------------------------------------=
-----
> Rapidly troubleshoot problems before they affect your business. Most IT
> organizations don't have a clear picture of how application performance
> affects their revenue. With AppDynamics, you get 100% visibility into you=
r
> Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics
> Pro!
> http://pubads.g.doubleclick.net/gampad/clk?id=3D84349831&iu=3D/4140/ostg.=
clktrk
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
--047d7b5d2ea437136304eed50d03
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Interesting. I think the original BitDNS discussion was mo=
re interesting that what currently is happening with namecoin, see <a href=
=3D"https://bitcointalk.org/index.php?topic=3D1790.0">https://bitcointalk.o=
rg/index.php?topic=3D1790.0</a> <br>
<br>Satoshi said there: "1) IP records don't need to be in the cha=
in, just do registrar function not DNS. =A0And CA problem solved, neat.&quo=
t; <br><br>Besides, ICANN is currently selling out the global public namesp=
ace - not that anybody really cares about such measly topics as the ownersh=
ip of global namespaces. And so some guy on the Cayman Islands is now the l=
argest holder of TLD's.<br>
<div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Tue, Dec 31, 2=
013 at 2:48 PM, Gregory Maxwell <span dir=3D"ltr"><<a href=3D"mailto:gma=
xwell@gmail.com" target=3D"_blank">gmaxwell@gmail.com</a>></span> wrote:=
<br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bor=
der-left:1px solid rgb(204,204,204);padding-left:1ex">
<div class=3D"im">On Tue, Dec 31, 2013 at 5:39 AM, Drak <<a href=3D"mail=
to:drak@zikula.org">drak@zikula.org</a>> wrote:<br>
> The NSA has the ability, right now to change every download of bitcoin=
-qt,<br>
> on the fly and the only cure is encryption.<br>
<br>
</div>Please cut it out with the snake oil pedaling. This is really over th=
e<br>
top. You're invoking the NSA as the threat here? Okay. The NSA can<br>
trivially compromise an HTTPS download site: even ignoring the CA<br>
insecurity, and government run CAs certificate authorities issue CA<br>
certs to random governments and corporations for dataloss prevention<br>
purposes. Not to mention unparalleled access to exploits.<br>
<br>
The downloads are protected by something far stronger than SSL<br>
already, which might even have a chance against the NSA. Actual<br>
signatures of the downloads with offline keys.<br>
<br>
I'm all pro-SSL and all that, but you are=97 piece by piece=97 really<b=
r>
convincing me that it produces an entirely false sense of security<br>
which is entirely unjustified.<br>
<br>
---------------------------------------------------------------------------=
---<br>
Rapidly troubleshoot problems before they affect your business. Most IT<br>
organizations don't have a clear picture of how application performance=
<br>
affects their revenue. With AppDynamics, you get 100% visibility into your<=
br>
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynami=
cs Pro!<br>
<a href=3D"http://pubads.g.doubleclick.net/gampad/clk?id=3D84349831&iu=
=3D/4140/ostg.clktrk" target=3D"_blank">http://pubads.g.doubleclick.net/gam=
pad/clk?id=3D84349831&iu=3D/4140/ostg.clktrk</a><br>
_______________________________________________<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-develo=
pment@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a><br>
</blockquote></div><br></div></div>
--047d7b5d2ea437136304eed50d03--
|
