blob: 30921eb2a7ed30fefce4f5e3788268e1efb7afeb (
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
64
65
66
67
68
69
70
71
72
73
74
75
76
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mh.in.england@gmail.com>) id 1TR829-0004MG-U1
for bitcoin-development@lists.sourceforge.net;
Wed, 24 Oct 2012 20:58:37 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.212.175 as permitted sender)
client-ip=209.85.212.175; envelope-from=mh.in.england@gmail.com;
helo=mail-wi0-f175.google.com;
Received: from mail-wi0-f175.google.com ([209.85.212.175])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1TR829-0001R7-0R
for bitcoin-development@lists.sourceforge.net;
Wed, 24 Oct 2012 20:58:37 +0000
Received: by mail-wi0-f175.google.com with SMTP id hq4so4105226wib.10
for <bitcoin-development@lists.sourceforge.net>;
Wed, 24 Oct 2012 13:58:31 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.216.201.156 with SMTP id b28mr10509573weo.4.1351112310921;
Wed, 24 Oct 2012 13:58:30 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.216.236.30 with HTTP; Wed, 24 Oct 2012 13:58:30 -0700 (PDT)
In-Reply-To: <CABsx9T2Oc+LeJjczG_U9u06gkQRmSP0J8Q_hEJv0oGQLnKFuJw@mail.gmail.com>
References: <CANEZrP0XALwBFJyZTzYd5xBp4MRrjv0s_y2tOXbO7UgjWF2HzA@mail.gmail.com>
<20121024162255.GA30290@vps7135.xlshosting.net>
<CANEZrP1sxtOb+czMtBTkmzngEwMYRqD667WyKQkAOKLi+mGBGQ@mail.gmail.com>
<20121024171104.GA31766@vps7135.xlshosting.net>
<CABsx9T0JyFJKLWK09NEzDk6B9Z2Yz7T55kf8GJ2o3ViCnBpRAw@mail.gmail.com>
<CANEZrP1AFL6ZbV7Njr1s8ggsZkQA1dv_3LYT3z+y83UKqn7Kgg@mail.gmail.com>
<CABsx9T2Oc+LeJjczG_U9u06gkQRmSP0J8Q_hEJv0oGQLnKFuJw@mail.gmail.com>
Date: Wed, 24 Oct 2012 22:58:30 +0200
X-Google-Sender-Auth: -FvMBwGYYzRtz-_huKwi1_0nrRA
Message-ID: <CANEZrP0KN6+Jh4Lc1Cs15a1zk6eKeXRZ7aEoeUDE148arvZw1Q@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Gavin Andresen <gavinandresen@gmail.com>
Content-Type: text/plain; charset=UTF-8
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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(mh.in.england[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
0.0 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1TR829-0001R7-0R
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Draft BIP for Bloom filtering
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: Wed, 24 Oct 2012 20:58:38 -0000
> What is the worst-case for an attacker interested in trying to get you
> to saturate your upstream bandwidth or use lots of memory? Set a
> bloom filter that matches everything, and then start requesting old
> blocks in the chain?
It would be slightly worse than shipping a full block but not seriously so.
If you just want to saturate bandwidth or disk IOPS you could probably
just request random blocks over and over again.
|
