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
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
|
Return-Path: <adam@cypherspace.org>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 19A7A3C8
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 31 Jul 2015 13:18:01 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from mout.perfora.net (mout.perfora.net [74.208.4.197])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 5F51115A
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 31 Jul 2015 13:18:00 +0000 (UTC)
Received: from mail-qk0-f181.google.com ([209.85.220.181]) by
mrelay.perfora.net (mreueus001) with ESMTPSA (Nemesis) id
0LoXz2-1YewlJ2Jgo-00gUI4 for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 31 Jul 2015 15:17:59 +0200
Received: by qkdg63 with SMTP id g63so28768902qkd.0
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 31 Jul 2015 06:17:58 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.55.24.226 with SMTP id 95mr4100520qky.74.1438348678701; Fri,
31 Jul 2015 06:17:58 -0700 (PDT)
Received: by 10.96.226.68 with HTTP; Fri, 31 Jul 2015 06:17:58 -0700 (PDT)
In-Reply-To: <20150731130714.Horde.PvL1IB3Kf5S6GAA73N-HOw1@server47.web-hosting.com>
References: <20150731083943.Horde.68uT9J78H_PdIgIwQP5frA1@server47.web-hosting.com>
<CALqxMTFhfwvcqY0dSoq489kA9G8YkQZPkzJDEU1eQHsupq-31g@mail.gmail.com>
<20150731130714.Horde.PvL1IB3Kf5S6GAA73N-HOw1@server47.web-hosting.com>
Date: Fri, 31 Jul 2015 15:17:58 +0200
Message-ID: <CALqxMTHFy0F6ov1_H+MkQ+6succ2pxqOWuYJkR57HBtRMU+AGQ@mail.gmail.com>
From: Adam Back <adam@cypherspace.org>
To: jl2012@xbt.hk
Content-Type: text/plain; charset=UTF-8
X-Provags-ID: V03:K0:sSJnPGfdG0LAB+CarEaraAdIUNkaQaBRg9sZsRSWFuLquuLFsmd
sZ+XFZ/b7fB93WVs9LpyaA7s4TOckbZCLhLIp4fDL+oNXEckybGmWwjU4H/WIB6YHwA8xJr
jEgOsy007vkScypseghgaEU5JkagTtlqOPEACu4Sfg183qJ+IxSQAeLvYqfr3WyW+YsDJmp
E9S04Yo2qTag0Q6gE2rFw==
X-UI-Out-Filterresults: notjunk:1;V01:K0:OV8MPaOdjAk=:l9Qc8gBiSJxTCSUIggx77e
ttLdP2FG4Iu1i27GL6fICsmOcw2f64H9KS6tY9vQCWBuKT2lk2TGEwe+Y/nb/s1nesA+p0aPg
IYYc6A2nqx3+wmM3S4dE35mTLToyXBIVz/9i2CueGTq/Uajpx3qlKmtlcPJ57zOKcwt/S9oDB
qpCM1kAdvSJtQW55topCxor94HNetC0IQdRMnlYqQQXlLxXoGaJJXA0PRJfZHNKKQmJdAOTK4
ySbvJvzqJO7a/EydrVjBA3AKWaZtZkqCp9oUzjLxIA74Ug3xC9xRvJZkE1oDqizeOvP8JGMoI
rOZD1hdLR8dZNm31JQmvt86om+WXtM5mOMUf5KPxudQqGwof5Zdve7YncTcVyn62EoTrx9C1W
8B1xGXxUxcYaGOvCbU6sYlBgJP5h3FvKw6vByWLeHQnVj8VxVA7TP8CeWyiltzLUP/8tSvxOQ
Xb/qMsWrurR/FgkxR+EFywXFDskxJU9McKnT7pCtuZgYDPqaUBnJkiC6LCDrKkmulfpAjfI3j
Q7tgGUAMFPGBrzufwxdgvqZoGqeiMyKVXrNOYFg/VKvPTbbKpSBafWazuiN9TAqSXGETqjik0
7/rGfQ7En8lbDQKUuKnjd4WPNF2nrZGMvN5q1t6Ii7FFRUXGW1+hvnmMgSJeCn2HRd5Lc2/yv
8RPlNIwHYsLLm34i18GIf/Ua5zXONtlFTZsJ3zMvuVi1MMA==
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW
autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] A compromise between BIP101 and Pieter's proposal
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Development Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Fri, 31 Jul 2015 13:18:01 -0000
That's all well and fine. But the pattern of your argument I would
say is "arguing security down" ie saying something is not secure
anyway, nothing is secure, everything could be hacked, so lets forget
that and give up, so that what is left is basically no
decentralisation security.
It is not paranoid to take decentralisation security seriously, it is
necessary because it is critical to Bitcoin. Security in depth
meaning take what security you can get from available defences.
Adam
On 31 July 2015 at 15:07, <jl2012@xbt.hk> wrote:
> Yes, data-center operators are bound to follow laws, including NSLs and gag
> orders. How about your ISP? Is it bound to follow laws, including NSLs and
> gag orders?
> https://edri.org/irish_isp_introduces_blocking/
>
> Do you think everyone should run a full node behind TOR? No way, your
> repressive government could just block TOR:
> http://www.technologyreview.com/view/427413/how-china-blocks-the-tor-anonymity-network/
>
> Or they could raid your home and seize your Raspberry Pi if they couldn't
> read your encrypted internet traffic. You will have a hard time proving you
> are not using TOR for child porn or cocaine.
> https://en.wikipedia.org/wiki/Encryption_ban_proposal_in_the_United_Kingdom
>
> If you are living in a country like this, running Bitcoin in an offshore VPS
> could be much easier. Anyway, Bitcoin shouldn't be your first thing to worry
> about. Revolution is probably your only choice.
>
> Data-centers would get hacked. How about your Raspberry Pi?
>
> Corrupt data-center employee is probably the only valid concern. However,
> there is nothing (except cost) to stop you from establishing multiple full
> nodes all over the world. If your Raspberry Pi at home could no longer fully
> validate the chain, it could become a header-only node to make sure your VPS
> full nodes are following the correct chaintip. You may even buy hourly
> charged cloud hosting in different countries to run header-only nodes at
> negligible cost.
>
> There is no single point of failure in a decentralized network. Having
> multiple nodes will also save you from Sybil attack and geopolitical risks.
> Again, if all data-centres and governments in the world are turning against
> Bitcoin, it is delusional to think we could fight against them without using
> any real weapon.
>
> By the way, I'm quite confident that my current full node at home are
> capable of running at 8MB blocks.
>
>
>
> Quoting Adam Back <adam@cypherspace.org>:
>
>> I think trust the data-center logic obviously fails, and I was talking
>> about this scenario in the post you are replying to. You are trusting the
>> data-center operator period. If one could trust data-centers to run
>> verified code, to not get hacked, filter traffic, respond to court orders
>> without notifying you etc that would be great but that's unfortunately not
>> what happens.
>>
>> Data-center operators are bound to follow laws, including NSLs and gag
>> orders. They also get hacked, employ humans who can be corrupt,
>> blackmailed, and themselves centralisation points for policy attack.
>> Snowden related disclosures and keeping aware of security show this is
>> very
>> real.
>>
>> This isn't much about bitcoin even, its just security reality for hosting
>> anything intended to be secure via decentralisation, or just hosting in
>> general while at risk of political or policy attack.
>>
>> Adam
>
>
>
|
