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
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <luke@dashjr.org>) id 1Vpdc7-00005R-2r
for bitcoin-development@lists.sourceforge.net;
Sun, 08 Dec 2013 12:37:35 +0000
X-ACL-Warn:
Received: from zinan.dashjr.org ([192.3.11.21])
by sog-mx-3.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
id 1Vpdc5-0006TT-5U for bitcoin-development@lists.sourceforge.net;
Sun, 08 Dec 2013 12:37:34 +0000
Received: from ishibashi.localnet (unknown
[IPv6:2001:470:5:265:be5f:f4ff:febf:4f76])
(Authenticated sender: luke-jr)
by zinan.dashjr.org (Postfix) with ESMTPSA id C91661080C8A;
Sun, 8 Dec 2013 12:37:39 +0000 (UTC)
From: "Luke-Jr" <luke@dashjr.org>
To: bitcoin-development@lists.sourceforge.net
Date: Sun, 8 Dec 2013 12:37:22 +0000
User-Agent: KMail/1.13.7 (Linux/3.12.1-gentoo; KDE/4.10.5; x86_64; ; )
References: <52A3C8A5.7010606@gmail.com>
<1795f3067ba3fcdd0caf978cc59ff024.squirrel@fruiteater.riseup.net>
<52A435EA.7090405@gmail.com>
In-Reply-To: <52A435EA.7090405@gmail.com>
X-PGP-Key-Fingerprint: E463 A93F 5F31 17EE DE6C 7316 BD02 9424 21F4 889F
X-PGP-Key-ID: BD02942421F4889F
X-PGP-Keyserver: hkp://pgp.mit.edu
MIME-Version: 1.0
Content-Type: Text/Plain;
charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Message-Id: <201312081237.24473.luke@dashjr.org>
X-Spam-Score: -0.1 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-0.1 RP_MATCHES_RCVD Envelope sender domain matches handover relay
domain
X-Headers-End: 1Vpdc5-0006TT-5U
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: Sun, 08 Dec 2013 12:37:35 -0000
On Sunday, December 08, 2013 9:03:38 AM Sa=C3=AFvann Carignan wrote:
> Binaries:
> Sourceforge is not encrypted, actually. Although binaries hosting /
> sharing could be a separate subject discussed later I think.
Encryption is useless here. We want everyone to be able to download Bitcoin=
=20
clients. Binaries on sourceforge are signed by multiple parties using gitia=
n.
> Decentralization:
> So long as we actually use DNS, the website is centralized :( However,
> its content isn't (can be forked on GitHub), but regarding the domain
> name, there is not much we can do against this AFAIK.
So long as someone has root (or a user that can modify it), the website is=
=20
centralised. To really solve this, we would need a dedicated server that=20
accepts commands only when signed by N-of-M parties, inside a cage locked b=
y=20
padlocks with keys held by independent parties, with a SSL certificate issu=
ed=20
by an authority that has multiple parties watch it every step of the way in=
to=20
that server.
Luke
|
