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
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <jtimon@monetize.io>) id 1Vz9N8-0004MZ-0f
for bitcoin-development@lists.sourceforge.net;
Fri, 03 Jan 2014 18:21:26 +0000
Received: from mail-lb0-f169.google.com ([209.85.217.169])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Vz9N6-0000vr-VW
for bitcoin-development@lists.sourceforge.net;
Fri, 03 Jan 2014 18:21:25 +0000
Received: by mail-lb0-f169.google.com with SMTP id u14so8463688lbd.0
for <bitcoin-development@lists.sourceforge.net>;
Fri, 03 Jan 2014 10:21:18 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:in-reply-to:references:date
:message-id:subject:from:to:cc:content-type;
bh=mgleVONfLeIq22hOpSpaRZMYGtlfxUM4VQcfWXy6WJU=;
b=RU1+3BrbC11lgZQR2u4mlM39FsW/eFqdEK2J04jkxjDoJXkOWswbFuOqvCishwhMgt
P7c4OHOR4gmeYdCVnWYPO24YsQsSw6jIPawYc83lH791WBGXKdbZ+ICAm5OKFT/c10Vo
w+HA2K5cjXXeJ4dyrt1UeE4nD8ctNyrBZ3DyLcvsoIZyi39h+kii0/1rIW+xgInX05RA
ABh/CzuQq/rVIf0Ln1/KNDLy4ZTYc97dkU4LbfANEJqsZB6w1RxsPTVrHhlNOj5mdNh9
QmcIJ4XsA8VfXF0q9zmC6KVQcezZEymdaCweD6u0DvO9LXDtbwmOzL4g7huJ98tfWn2m
HuMQ==
X-Gm-Message-State: ALoCoQnRg+5bXrbE7ie9N+bzqnroyzmAd+KqelduFfliE+shEXr2kExiwR1u2ke9UTuTWrqSvZCl
MIME-Version: 1.0
X-Received: by 10.152.116.65 with SMTP id ju1mr1163679lab.60.1388773278138;
Fri, 03 Jan 2014 10:21:18 -0800 (PST)
Received: by 10.112.74.71 with HTTP; Fri, 3 Jan 2014 10:21:17 -0800 (PST)
X-Originating-IP: [85.53.148.187]
In-Reply-To: <20140103173817.GN3180@nl.grid.coop>
References: <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>
<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>
Date: Fri, 3 Jan 2014 19:21:17 +0100
Message-ID: <CAC1+kJMHaZWCjhqZMRBqpZ4O1kBLqSV1eig7e_LqOYK8T_e_4Q@mail.gmail.com>
From: =?ISO-8859-1?Q?Jorge_Tim=F3n?= <jtimon@monetize.io>
To: Troy Benjegerdes <hozer@hozed.org>
Content-Type: text/plain; charset=ISO-8859-1
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
X-Headers-End: 1Vz9N6-0000vr-VW
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: Fri, 03 Jan 2014 18:21:26 -0000
On 1/3/14, Troy Benjegerdes <hozer@hozed.org> wrote:
> 'make' should check the hash.
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.
> The binary should check it's own hash.
I'm afraid this is not possible.
> The operating system should check the hash.
There's package management systems like apt-secure that do exactly this.
|
