Is there a measure in place to prevent an adversary from connecting to a Bitcoin node many times in parallel, thus saturating its open connection slots?
Add a comment
|
1 Answer
The measure is that the node running bitcoin removes the cap to the number connection slots. The cap for connection slots I have found is set to no limit when running a bitcoin service.
Sorry I stand corrected, back in 2011 looks like a cap of 125 connections was introduced Is there a connections limit on bitcoind?
in the net.cpp file https://bitcointalk.org/index.php?topic=52772.msg629593#msg629593
but this has since been changed and I dont think there is a cap anymore... Looking at the file looks like this is the area you are interested in: https://github.com/bitcoin/bitcoin/blob/master/src/net.cpp#L1081 and the values set here https://github.com/bitcoin/bitcoin/blob/master/src/net.h
-
How can removing the cap help? Can you point me to the source code? Commented Apr 17, 2018 at 12:52
-
Ok, I am aware of the 8 outgoing + 117 incoming connections limit, my question is, is there anything that prevents me from connecting to a chosen node up to 117 times from the same IP, if its connection slots are free? Commented Apr 17, 2018 at 13:57
-
I think that one node would see your 117 connections from the same ip and just block your ip on connecting. It would seem there is no limit in the code from the discussion here bitcointalk.org/index.php?topic=765157.0 Commented Apr 17, 2018 at 15:05
-
But it would have to be done by a firewall or some other software independent of the Bitcoin client, right? Commented Apr 17, 2018 at 19:12
-
Yeh as far as I can see there is nothing in the code to prevent the situation as u describe Commented Apr 18, 2018 at 8:40