blob: a115cd02ca12f4020b791f821a892fa25268a240 (
plain)
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
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <eugen@leitl.org>) id 1WmlAQ-0000vq-Rc
for bitcoin-development@lists.sourceforge.net;
Tue, 20 May 2014 14:37:22 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of leitl.org
designates 164.177.174.8 as permitted sender)
client-ip=164.177.174.8; envelope-from=eugen@leitl.org;
helo=leitl.org;
Received: from v8.ativel.com ([164.177.174.8] helo=leitl.org)
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256)
(Exim 4.76) id 1WmlAO-0004MW-2u
for bitcoin-development@lists.sourceforge.net;
Tue, 20 May 2014 14:37:22 +0000
Received: by leitl.org (Postfix, from userid 1000)
id DB19F540022; Tue, 20 May 2014 16:37:10 +0200 (CEST)
Date: Tue, 20 May 2014 16:37:10 +0200
From: Eugen Leitl <eugen@leitl.org>
To: bitcoin-development@lists.sourceforge.net
Message-ID: <20140520143710.GT26986@leitl.org>
References: <CANEZrP2rgiQHpekEpFviJ22QsiV+s-F2pqosaZOA5WrRtJx5pg@mail.gmail.com>
<CANAnSg0ABVyRcSaO2aEcqO8qaj+JdxRN4z-hLE-EbESv2TMf2g@mail.gmail.com>
<trinity-1957ed0e-a607-47d7-803b-71c59af8eb89-1400573744536@3capp-mailcom-bs08>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <trinity-1957ed0e-a607-47d7-803b-71c59af8eb89-1400573744536@3capp-mailcom-bs08>
User-Agent: Mutt/1.5.21 (2010-09-15)
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: -1.5 (-)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
-0.0 SPF_HELO_PASS SPF: HELO matches SPF record
-0.0 SPF_PASS SPF: sender matches SPF record
X-Headers-End: 1WmlAO-0004MW-2u
Subject: Re: [Bitcoin-development] Why are we bleeding nodes?
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: Tue, 20 May 2014 14:37:23 -0000
On Tue, May 20, 2014 at 10:15:44AM +0200, bitcoingrant@gmx.com wrote:
> Recently China has updated its firewall blocking bitcoin sites and p=
ools.
> Whether this is simple blacklist or more=C2=A0sophisticated=C2=A0pac=
ket targeting is
> uncertain, however this update did spefically target VPN handshakes.
Could a blockchain fork due to network split happen?
=C2=A0
|
