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-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <showard314@gmail.com>) id 1UOrQa-0002Kp-3V
for bitcoin-development@lists.sourceforge.net;
Sun, 07 Apr 2013 15:22:44 +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=showard314@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 1UOrQU-00083S-L1
for bitcoin-development@lists.sourceforge.net;
Sun, 07 Apr 2013 15:22:44 +0000
Received: by mail-wi0-f175.google.com with SMTP id c10so1861217wiw.2
for <bitcoin-development@lists.sourceforge.net>;
Sun, 07 Apr 2013 08:22:32 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.180.94.39 with SMTP id cz7mr8324793wib.21.1365348152441;
Sun, 07 Apr 2013 08:22:32 -0700 (PDT)
Received: by 10.194.104.104 with HTTP; Sun, 7 Apr 2013 08:22:32 -0700 (PDT)
In-Reply-To: <51618612.9010603@olivere.de>
References: <51618612.9010603@olivere.de>
Date: Sun, 7 Apr 2013 11:22:32 -0400
Message-ID: <CANg8-dC2FX-9QFE_Bq6djTiEsvvD+0Cc2Vy0Ofzk54DVrdVuxA@mail.gmail.com>
From: Scott Howard <showard314@gmail.com>
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Content-Type: text/plain; charset=ISO-8859-1
X-Spam-Score: -0.1 (/)
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
(showard314[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
0.2 FREEMAIL_ENVFROM_END_DIGIT Envelope-from freemail username ends in
digit (showard314[at]gmail.com)
1.2 MISSING_HEADERS Missing To: header
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
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
X-Headers-End: 1UOrQU-00083S-L1
Subject: Re: [Bitcoin-development] DOS-Attacks on bitcoin-client?
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, 07 Apr 2013 15:22:44 -0000
On Sun, Apr 7, 2013 at 10:43 AM, Oliver Egginger <bitcoin@olivere.de> wrote:
> Hello,
>
> I'm using your bitcoin-qt client (version 0.8.1). Normally everything is
> working pretty fine, but sometimes it seems that other nodes produce an
> enormous amount of traffic. I have not had the time to investigate
> thoroughly yet. I only have briefly viewed with tshark.
>
> So far I have just restarted the client in the hope that it no longer
> connects with the 'evil' node. This usually works quite well.
>
> Is anything about DOS-Attacks known to you?
Many new users have started using the reference client which downloads
the whole blockchain from peers. There currently isn't a throttling
mechanism [1] so it's possible to quickly eat up your bandwidth. You
can try QoS on your router or use the -nolisten command line flag. You
will still relay transactions, just not serve the whole blockchain.
[1] https://github.com/bitcoin/bitcoin/issues/273
|
