diff options
author | Jeff Garzik <jgarzik@bitpay.com> | 2013-11-22 16:01:51 -0500 |
---|---|---|
committer | bitcoindev <bitcoindev@gnusha.org> | 2013-11-22 21:01:58 +0000 |
commit | 6782702d7d0a98c8d06253afdacdac291d00f2e8 (patch) | |
tree | 02ade9b38513b00f51f11919e9078f1308ddad84 | |
parent | 3027c873f3265533c85db77348eb45c898f7dafe (diff) | |
download | pi-bitcoindev-6782702d7d0a98c8d06253afdacdac291d00f2e8.tar.gz pi-bitcoindev-6782702d7d0a98c8d06253afdacdac291d00f2e8.zip |
Re: [Bitcoin-development] [PATCH, try2] bitcoind: whitelist nodes against banning
-rw-r--r-- | 0f/fac8090284fe9b6b1b90d356635abf132dda77 | 86 |
1 files changed, 86 insertions, 0 deletions
diff --git a/0f/fac8090284fe9b6b1b90d356635abf132dda77 b/0f/fac8090284fe9b6b1b90d356635abf132dda77 new file mode 100644 index 000000000..437767f56 --- /dev/null +++ b/0f/fac8090284fe9b6b1b90d356635abf132dda77 @@ -0,0 +1,86 @@ +Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] + helo=mx.sourceforge.net) + by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) + (envelope-from <jgarzik@bitpay.com>) id 1VjxrS-0004qC-7s + for bitcoin-development@lists.sourceforge.net; + Fri, 22 Nov 2013 21:01:58 +0000 +Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of bitpay.com + designates 74.125.82.178 as permitted sender) + client-ip=74.125.82.178; envelope-from=jgarzik@bitpay.com; + helo=mail-we0-f178.google.com; +Received: from mail-we0-f178.google.com ([74.125.82.178]) + by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) + (Exim 4.76) id 1VjxrR-00007L-GT + for bitcoin-development@lists.sourceforge.net; + Fri, 22 Nov 2013 21:01:58 +0000 +Received: by mail-we0-f178.google.com with SMTP id u56so1653526wes.37 + for <bitcoin-development@lists.sourceforge.net>; + Fri, 22 Nov 2013 13:01:51 -0800 (PST) +X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; + d=1e100.net; s=20130820; + h=x-gm-message-state:mime-version:in-reply-to:references:date + :message-id:subject:from:to:cc:content-type; + bh=I0RNHpIoVRJFuG9rxoLU9aDB+kbbcIaSf9IKIbfFMdw=; + b=RNp81UC7hbSVgN9RJEsxMh/897dkJbJQX9qCA0QbaE9R8iP2DccAx9XSunIzlGanR7 + nY7C0i72g9foyMpa4448nUv23R7fT1PEx2VxSS5v7gBlEuHypA40cT7WAi+kpCMpAeEz + 2L87AikTdZlR6bD5n6xr6hyQd5aUwO3UuXt1I8Ti7qSwbqcsv5e7ZZzPh5h36FtG4CpC + O3omL8hA7Q3WNeN3mecyLRPaKrzSC5oi+K48OdfXLdTgzngHJbAf/hli6T5/zxu48fw8 + rtJhb9dn8286zixzwo2oxDeXmj044YprbbRFXTAkwj3Esuv+awmTAsMo8pWlWVxv1Afo + 83zg== +X-Gm-Message-State: ALoCoQk39atLJcgywEF2z4vMQtx8J8r8SAtbD3cJu4wuPhtNQl9igN5iBxALolcBKtF79iAXgnxK +MIME-Version: 1.0 +X-Received: by 10.180.11.37 with SMTP id n5mr4204665wib.25.1385154111181; Fri, + 22 Nov 2013 13:01:51 -0800 (PST) +Received: by 10.194.164.164 with HTTP; Fri, 22 Nov 2013 13:01:51 -0800 (PST) +In-Reply-To: <CAAS2fgRp7K7QD+y7a5uQr-BneN2MfW5U3J4NeoF9T_WcFv+UPg@mail.gmail.com> +References: <CAJHLa0NGQaMMFByzHhnuPHYhUSj6czqBcimwhaj-DyEM91PRZA@mail.gmail.com> + <CAAS2fgRp7K7QD+y7a5uQr-BneN2MfW5U3J4NeoF9T_WcFv+UPg@mail.gmail.com> +Date: Fri, 22 Nov 2013 16:01:51 -0500 +Message-ID: <CAJHLa0NJxFOo2ZAv86bcMTNwjNJNL1v3bVmN6f+3MEnWfs5dcg@mail.gmail.com> +From: Jeff Garzik <jgarzik@bitpay.com> +To: Gregory Maxwell <gmaxwell@gmail.com> +Content-Type: text/plain; charset=ISO-8859-1 +X-Spam-Score: -1.6 (-) +X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. + See http://spamassassin.org/tag/ for more details. + 0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked. + See + http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block + for more information. [URIs: bitpay.com] + -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for + sender-domain + -0.0 SPF_PASS SPF: sender matches SPF record + -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: 1VjxrR-00007L-GT +Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net> +Subject: Re: [Bitcoin-development] [PATCH, + try2] bitcoind: whitelist nodes against banning +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: Fri, 22 Nov 2013 21:01:58 -0000 + +On Fri, Nov 22, 2013 at 3:56 PM, Gregory Maxwell <gmaxwell@gmail.com> wrote: +> Is there a reason not to have a parallel get rpc to get the current list? + +Easy enough to add. There had also been requests for an IP blacklist, +which would need associated RPC/config gadgetry. + +-- +Jeff Garzik +Bitcoin core developer and open source evangelist +BitPay, Inc. https://bitpay.com/ + + |