Pieter Wuille dc942e6f27 Introduce whitelisted peers. ... This adds a -whitelist option to specify subnet ranges from which peers that connect are whitelisted. In addition, there is a -whitebind option which works like -bind, except peers connecting to it are also whitelisted (allowing a separate listen port for trusted connections). Being whitelisted has two effects (for now): * They are immune to DoS disconnection/banning. * Transactions they broadcast (which are valid) are always relayed, even if they were already in the mempool. This means that a node can function as a gateway for a local network, and that rebroadcasts from the local network will work as expected. Whitelisting replaces the magic exemption localhost had for DoS disconnection (local addresses are still never banned, though), which implied hidden service connects (from a localhost Tor node) were incorrectly immune to DoS disconnection as well. This old behaviour is removed for that reason, but can be restored using -whitelist=127.0.0.1 or -whitelist=::1 can be specified. -whitebind is safer to use in case non-trusted localhost connections are expected (like hidden services).		2014-07-09 20:40:14 +02:00
..
build-tests.sh.in	Have pull-tester run the listtransactions.py regression test	2014-04-02 19:59:17 -04:00
pull-tester.py	Add licenses for tests and test data	2014-03-18 10:20:55 +01:00
pull-tester.sh	stop bitcoind/bitcoin-cli processes that might have been left running	2014-05-02 12:37:20 -04:00
run-bitcoind-for-test.sh.in	Introduce whitelisted peers.	2014-07-09 20:40:14 +02:00