From mboxrd@z Thu Jan  1 00:00:00 1970
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 <hozer@grid.coop>) id 1VzGHE-0004aA-1v
	for bitcoin-development@lists.sourceforge.net;
	Sat, 04 Jan 2014 01:43:48 +0000
X-ACL-Warn: 
Received: from nl.grid.coop ([50.7.166.116])
	by sog-mx-4.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
	id 1VzGH9-0003qw-SO for bitcoin-development@lists.sourceforge.net;
	Sat, 04 Jan 2014 01:43:48 +0000
Received: from localhost (localhost [127.0.0.1]) (uid 1000)
	by nl.grid.coop with local; Fri, 03 Jan 2014 19:43:36 -0600
	id 000000000006E269.0000000052C76748.00007691
Date: Fri, 3 Jan 2014 19:43:36 -0600
From: Troy Benjegerdes <hozer@hozed.org>
To: Jorge =?iso-8859-1?Q?Tim=F3n?= <jtimon@monetize.io>
Message-ID: <20140104014336.GO3180@nl.grid.coop>
References: <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>
	<20140103054515.GL3180@nl.grid.coop>
	<CANAnSg0esEMQ+G=9F2zK6okcewT6NdYBFnXHmyHz8VR4AAp0nw@mail.gmail.com>
	<20140103173817.GN3180@nl.grid.coop>
	<CAC1+kJMHaZWCjhqZMRBqpZ4O1kBLqSV1eig7e_LqOYK8T_e_4Q@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
In-Reply-To: <CAC1+kJMHaZWCjhqZMRBqpZ4O1kBLqSV1eig7e_LqOYK8T_e_4Q@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Mime-Autoconverted: from 8bit to quoted-printable by courier 0.68.2
X-Spam-Score: -0.5 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	-0.5 RP_MATCHES_RCVD Envelope sender domain matches handover relay
	domain
X-Headers-End: 1VzGH9-0003qw-SO
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: Sat, 04 Jan 2014 01:43:48 -0000

On Fri, Jan 03, 2014 at 07:21:17PM +0100, Jorge Tim=F3n wrote:
> On 1/3/14, Troy Benjegerdes <hozer@hozed.org> wrote:
> > 'make' should check the hash.
>=20
> An attacker could replace that part of the makefile.
> Anyway, I think this is more oriented for compiled binaries, not for
> people downloading the sources. I assume most of that people just use
> git.
>=20
> > The binary should check it's own hash.
>=20
> I'm afraid this is not possible.
>
> > The operating system should check the hash.
>=20
> There's package management systems like apt-secure that do exactly this=
.

Yes. Promoting operating systems (and signed .deb packages) is a far bett=
er
thing to do than worrying about TLS on the bitcoin.org server.