Shy clients #101

1. 
   gavinandresen commented at 10:15 pm on March 5, 2011: contributor

   Shy client patch from Hal Finney: “On incoming connections, it won’t send a version message until it receives one. This can help make port scanning identification harder.”
2. shy patch from Hal cbc920d474
3. 
   jgarzik commented at 8:26 pm on March 9, 2011: contributor

   How do deployed clients behave, in reaction to this behavior change?
4. 
   gavinandresen commented at 5:46 pm on March 14, 2011: contributor

   Deployed clients behave just fine– they just wait for the connecting node to send a version message first, instead of both ends sending a version message right away.

   I’m going to run this (along with several other patches) on the Faucet machines, then plan on pulling it.

5. glv2 referenced this in commit 850bf0a6d0 on Aug 8, 2014
6. rdponticelli referenced this in commit f79d80a724 on Nov 26, 2014
7. zathras-crypto referenced this in commit 44ea346fb5 on Jun 27, 2015
8. TheBlueMatt referenced this in commit caba3002d5 on Oct 3, 2016
9. classesjack referenced this in commit 6d89734765 on Jan 2, 2018
10. 0xartem referenced this in commit 4b4ee84dac on Jan 19, 2018
11. cryptapus referenced this in commit 4fac08d077 on Aug 27, 2018
12. lateminer referenced this in commit 35540856f5 on Feb 23, 2019
13. attilaaf referenced this in commit 22e7f5d7d5 on Jan 13, 2020
14. Losangelosgenetics referenced this in commit 94f1d8fc76 on Mar 12, 2020
15. rajarshimaitra referenced this in commit 139df5e5d2 on Mar 23, 2021
16. rajarshimaitra referenced this in commit 32bc63ae9b on Aug 5, 2021
17. rajarshimaitra referenced this in commit f0f78b4f7f on Aug 5, 2021
18. DrahtBot locked this on Sep 8, 2021

Contributors
gavinandresen jgarzik