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
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mh.in.england@gmail.com>) id 1VpnOG-0001Ph-Ly
for bitcoin-development@lists.sourceforge.net;
Sun, 08 Dec 2013 23:03:56 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.214.172 as permitted sender)
client-ip=209.85.214.172; envelope-from=mh.in.england@gmail.com;
helo=mail-ob0-f172.google.com;
Received: from mail-ob0-f172.google.com ([209.85.214.172])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1VpnOF-0006C3-QP
for bitcoin-development@lists.sourceforge.net;
Sun, 08 Dec 2013 23:03:56 +0000
Received: by mail-ob0-f172.google.com with SMTP id gq1so2993334obb.31
for <bitcoin-development@lists.sourceforge.net>;
Sun, 08 Dec 2013 15:03:50 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.182.219.167 with SMTP id pp7mr10615obc.85.1386543830405;
Sun, 08 Dec 2013 15:03:50 -0800 (PST)
Sender: mh.in.england@gmail.com
Received: by 10.76.92.72 with HTTP; Sun, 8 Dec 2013 15:03:50 -0800 (PST)
In-Reply-To: <20131208215850.GE62848@giles.gnomon.org.uk>
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>
<CANEZrP3+AowZZS1=hAkx0KODiT-vbcRKyZaHOE2CWaJk3y5-Dw@mail.gmail.com>
<52A4E199.3000209@gmail.com>
<20131208215850.GE62848@giles.gnomon.org.uk>
Date: Mon, 9 Dec 2013 00:03:50 +0100
X-Google-Sender-Auth: Hk7umlZxqU1R6EgQWEiMu2hGa40
Message-ID: <CANEZrP0YyLd-zwniE-FUT4AG2Zemp2SBrwF8gskTf3LgsKfByw@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Roy Badami <roy@gnomon.org.uk>
Content-Type: multipart/alternative; boundary=089e0141ab827a17ec04ed0de45f
X-Spam-Score: -0.5 (/)
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: bitcoin.org]
-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
(mh.in.england[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
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: 1VpnOF-0006C3-QP
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: Sun, 08 Dec 2013 23:03:56 -0000
--089e0141ab827a17ec04ed0de45f
Content-Type: text/plain; charset=UTF-8
> That's an interesting question. The bitcoin.org domain is hiding
> behind a WhoisGuard anonymous registration. Why are we not allowed to
> know who this domain belongs to? Why are we being asked to trust some
> unidentified party?
It's done that way because it was originally registered by Satoshi. It's
now controlled by Sirius, who doesn't really take part in the project
anymore.
I bring this up because of the recent bitcointalk fiasco. AFAIK the domains
are registered and controlled in the same way. It's likely that the current
registrar isn't very secure.
--089e0141ab827a17ec04ed0de45f
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><br><div class=3D"gmail_extra"><div class=3D"gmail_quote">=
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">That's an interesting question. =C2=A0Th=
e <a href=3D"http://bitcoin.org" target=3D"_blank">bitcoin.org</a> domain i=
s hiding<br>
behind a WhoisGuard anonymous registration. =C2=A0Why are we not allowed to=
<br>
know who this domain belongs to? =C2=A0Why are we being asked to trust some=
<br>
unidentified party?</blockquote><div><br></div><div>It's done that way =
because it was originally registered by Satoshi. It's now controlled by=
Sirius, who doesn't really take part in the project anymore.</div>
<div><br></div><div>I bring this up because of the recent bitcointalk fiasc=
o. AFAIK the domains are registered and controlled in the same way. It'=
s likely that the current registrar isn't very secure.</div></div></div=
>
</div>
--089e0141ab827a17ec04ed0de45f--
|
