The Windows Client had it’s own static IP with port 8333 open for it, I could see from the gateway device that it was connecting out to other peers and other peers were connecting back in. But after the 8, it’s like it quit connecting out to peers and after a while the incoming peers stopped as well since it appeared to only be concerned with the peers on the LAN vs the WAN. The behavior of the Linux client is different though I’ve noticed, even if 50 people are connected to it, it will still seek outbound connections to other peers and inbound peers continue to trickle in as well.

While this will only be a problem for people like me that have hundreds of PCs at their disposal, the reverse is, one could setup PC(s) to connect to a single client 8 or more times and then after a while, the poor windows client would suck itself into it’s own matrix world where it thinks it’s on the network solving blocks, but it’s really trapped back in time.

This is just a theoretical attack of course, I’m not going to lose any sleep over it, but I figured I would throw it out there for the future. The easiest way to negate this would be to put in some self-checking code for IPs. Basically, have to check that is has 8 connections or more that are NOT from the LAN/Same IP Address/etc when it’s running as a dual node/client mode.

I uploaded windows 0.3.1 rc1 and linux 0.3.1 rc2 to SourceForge and updated the links on the homepage.

You don’t need to update to 0.3.1 unless you had one of the problems listed in the first post.  If you’ve got it working already, stay with 0.3.0.

79,029 total views, 14 views today

https://bitcointalk.org/index.php?topic=383.msg3590#msg3590