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-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1R4Fkq-0005AJ-4m for bitcoin-development@lists.sourceforge.net; Thu, 15 Sep 2011 17:29:40 +0000 X-ACL-Warn: Received: from zinan.dashjr.org ([173.242.112.54]) by sog-mx-1.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1R4Fkn-00065j-Ah for bitcoin-development@lists.sourceforge.net; Thu, 15 Sep 2011 17:29:40 +0000 Received: from ishibashi.localnet (fl-184-4-160-40.dhcp.embarqhsd.net [184.4.160.40]) (Authenticated sender: luke-jr) by zinan.dashjr.org (Postfix) with ESMTPSA id D60A920403A; Thu, 15 Sep 2011 17:29:26 +0000 (UTC) From: "Luke-Jr" To: kjj Date: Thu, 15 Sep 2011 13:29:16 -0400 User-Agent: KMail/1.13.7 (Linux/2.6.39-gentoo; KDE/4.6.5; x86_64; ; ) References: <201109151136.47485.luke@dashjr.org> <4E722215.40401@jerviss.org> In-Reply-To: <4E722215.40401@jerviss.org> X-PGP-Key-Fingerprint: CE5A D56A 36CC 69FA E7D2 3558 665F C11D D53E 9583 X-PGP-Key-ID: 665FC11DD53E9583 X-PGP-Keyserver: x-hkp://subkeys.pgp.net MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201109151329.21849.luke@dashjr.org> X-Spam-Score: -0.5 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -0.5 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain X-Headers-End: 1R4Fkn-00065j-Ah 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 17:29:40 -0000 On Thursday, September 15, 2011 12:04:37 PM kjj wrote: > On the other hand, the vast, vast majority of all transactions follow a > particular pattern. If someone gives you one that doesn't match the > standard pattern, you might be a little suspicious, but it is no big > deal. But, if they emit dozens or hundreds, it is hardly unreasonable > to disconnect them until you figure out what's going on. That would make sense if you knew the node was originating them, MAYBE-- but not given the fact that they may merely be relaying transactions.