I ran a few searches across the forum but could not find an answer to this: How does the Bitcoin client handle bad peers (Other than rejecting bad TX and Blocks)?
If this functionality is not already built into the client, I would like to suggest this simple approach that frees up connections with bad peers:If PEER_IP sends more than REJECT_THRESHOLD malicious transactions or blocks within past 24 hours, Ban(PEER_IP) for 24 hours.Net Neutrality:
Many countries around the world have poor record on net neutrality, with selective blocking and government-run snooping programs. Recent case in point: Egypt.
I wholeheartedly throw my newbie support behind Madhatter's recommendations to:
- Use SSL connections
- Randomizing ports at start-up
- Populating SSL connect descriptors as "Apache" and "Firefox / Internet Explorer"