Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.217.176 as permitted sender)
	client-ip=209.85.217.176; envelope-from=gmaxwell@gmail.com;
	helo=mail-lb0-f176.google.com; 
MIME-Version: 1.0
In-Reply-To: <20130303185446.GU68379@giles.gnomon.org.uk>
References: <5132558A.8040304@recessionstories.net>
	<CABsx9T2yka9vHVttyzTuAEdHtmQSCyAPnJsh1EiwBNoiC24fSg@mail.gmail.com>
	<20130303185446.GU68379@giles.gnomon.org.uk>
Date: Sun, 3 Mar 2013 12:02:24 -0800
Message-ID: <CAAS2fgSRYcC4e0E5UiXnLUYZHOkRkvgVdRnmOBWfqcXEKdkgFQ@mail.gmail.com>
From: Gregory Maxwell <gmaxwell@gmail.com>
To: Roy Badami <roy@gnomon.org.uk>
Content-Type: text/plain; charset=UTF-8
Cc: g@gnomon.org.uk, bitcoin list <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Secure download
Precedence: list

On Sun, Mar 3, 2013 at 10:54 AM, Roy Badami <roy@gnomon.org.uk> wrote:
> Would be nice to have a secure page at bitcoin.org, though, rathar
> than having to go to github - certs from somewhere like Namecheap
> should cost you next to nothing.  For those of us too lazy (not
> paranoid enough) to bother with GPG, a (secure) page on bitoin.org
> with the MD5 hashes of the binaries would be awesome...

While I think that it's silly that we don't have a HTTPS (only!) page,
it should be noted that an HTTPS page is in no way a replacement for
GPG, sadly:  Anyone who can MITM the server to the whole internet can
trivially obtain a fraudulent cert with only moderate cost and time.

(The reason for this is that (many? most? all?) CAs verify authority
by having you place a file at some HTTP path on the domain in
question. Effectively the current CA model only prevents those from
intercepting who cannot intercept the traffic generally. Basically
only helps with the evil hotspot/tor_exit problem.)