Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1VpnLO-0000aI-4P for bitcoin-development@lists.sourceforge.net; Sun, 08 Dec 2013 23:00:58 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of mckay.com designates 37.1.88.131 as permitted sender) client-ip=37.1.88.131; envelope-from=robert@mckay.com; helo=mail.mckay.com; Received: from mail.mckay.com ([37.1.88.131]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) id 1VpnLJ-000645-N3 for bitcoin-development@lists.sourceforge.net; Sun, 08 Dec 2013 23:00:58 +0000 Received: from www-data by mail.mckay.com with local (Exim 4.76) (envelope-from ) id 1Vpmon-0007E5-PI; Sun, 08 Dec 2013 22:27:17 +0000 To: Gregory Maxwell X-PHP-Originating-Script: 0:func.inc MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Date: Sun, 08 Dec 2013 22:27:17 +0000 From: Robert McKay In-Reply-To: References: <52A3C8A5.7010606@gmail.com> <1795f3067ba3fcdd0caf978cc59ff024.squirrel@fruiteater.riseup.net> <52A435EA.7090405@gmail.com> <201312081237.24473.luke@dashjr.org> Message-ID: <261ae2bf5c67d44d090709be57a9e1ad@webmail.mckay.com> X-Sender: robert@mckay.com User-Agent: Roundcube Webmail/0.5.3 X-Spam-Score: -1.7 (-) 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 -0.1 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain 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: mckay.com] -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: 1VpnLJ-000645-N3 Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] =?utf-8?q?Dedicated_server_for_bitcoin=2Eor?= =?utf-8?q?g=2C_your_thoughts=3F?= 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:00:58 -0000 On Sun, 8 Dec 2013 13:14:44 -0800, Gregory Maxwell wrote: > On Sun, Dec 8, 2013 at 1:07 PM, Drak wrote: >> Simple verification relies on being able to answer the email sent to >> the >> person in the whois records, or standard admin/webmaster@ addresses >> to prove >> ownership of the domain > > Godaddy and many other CA's are verified from nothing other than a > http fetch, no email involved. It's just as easy to steal emails via a BGP or DNS redirect anyway.. you could even take over the actual domain at the registry level by stealing a password reset via BGP or DNS redirect and actually many registries will hand over control of a domain by faxing them a forged driving license in the owner's name anyway so it doesn't even really need to be a particularly sophisticated attacker. Once you have registry control of the domain it's easy enough to get an SSL cert too, probably even an 'extended validation' one. When Afghanistan was taken over the entire .af TLD was probably transferred using a forged fax to ICANN (http://web.archive.org/web/20041017031020/http://www.iana.org/cctld/af/razeeq-letter-13aug02.pdf) but I guess that's a little different :p Rob