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 ) 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 ; 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> <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: From: Mike Hearn To: Roy Badami 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 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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

=
That's an interesting question. =C2=A0Th= e bitcoin.org domain i= s hiding
behind a WhoisGuard anonymous registration. =C2=A0Why are we not allowed to=
know who this domain belongs to? =C2=A0Why 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 fiasc= o. AFAIK the domains are registered and controlled in the same way. It'= s likely that the current registrar isn't very secure.
--089e0141ab827a17ec04ed0de45f--