From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1R4Eh4-0005RP-1U for bitcoin-development@lists.sourceforge.net; Thu, 15 Sep 2011 16:21:42 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com designates 74.125.82.175 as permitted sender) client-ip=74.125.82.175; envelope-from=mh.in.england@gmail.com; helo=mail-wy0-f175.google.com; Received: from mail-wy0-f175.google.com ([74.125.82.175]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1R4Eh3-0003v9-7J for bitcoin-development@lists.sourceforge.net; Thu, 15 Sep 2011 16:21:42 +0000 Received: by wyh5 with SMTP id 5so1690906wyh.34 for ; Thu, 15 Sep 2011 09:21:35 -0700 (PDT) MIME-Version: 1.0 Received: by 10.216.178.194 with SMTP id f44mr584332wem.110.1316103695007; Thu, 15 Sep 2011 09:21:35 -0700 (PDT) Sender: mh.in.england@gmail.com Received: by 10.216.52.81 with HTTP; Thu, 15 Sep 2011 09:21:34 -0700 (PDT) In-Reply-To: References: <4E71F6D6.2090208@justmoon.de> Date: Thu, 15 Sep 2011 18:21:34 +0200 X-Google-Sender-Auth: a4xZND1nMmu4bSRT9R3uMPAhgQo Message-ID: From: Mike Hearn To: Gavin Andresen Content-Type: text/plain; charset=UTF-8 X-Spam-Score: -1.0 (-) 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.5 AWL AWL: From: address is in the auto white-list X-Headers-End: 1R4Eh3-0003v9-7J Cc: bitcoin-development@lists.sourceforge.net Subject: Re: [Bitcoin-development] Request review: drop misbehaving peers X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Sep 2011 16:21:42 -0000 > If I think you're trying to DoS me, why would I be nice to you? The issue is, what if I'm not trying to DoS you, but something went wrong? > think response messages would just give an attacker another potential > attack vector, and it is clear from the debug.log what triggers a ban. Only clear to the node owner. Not the sender, who may in a better position to debug. It's pretty common for protocols to return useful errors even in DoS conditions. Eg, http servers will often return 503 Service Unavailable in overload conditions. Google actually sends a redirect telling you why you got blocked.