Re: Antbleed: A remote shutdown backdoor in antminers

You'd think that if bitmain were to cease development on minerlink, they would remove all related code, or even announce that they are working on a fix.

Great to see there are people looking out for these exploits, but I think bitmain really screwed up here.

has anyone looked at bitcoin cores DNS seed managed by mainly blockstreamers

   vSeeds.push_back(CDNSSeedData("bitcoin.sipa.be", "seed.bitcoin.sipa.be", true)); // Pieter Wuille, only supports x1, x5, x9, and xd
   vSeeds.push_back(CDNSSeedData("bluematt.me", "dnsseed.bluematt.me", true)); // Matt Corallo, only supports x9
   vSeeds.push_back(CDNSSeedData("dashjr.org", "dnsseed.bitcoin.dashjr.org")); // Luke Dashjr

Looked.

Now what the purpose of the above?

It's one method used by Bitcoin to find out the IP of other nodes. There is a risk that the DNS seeds could co-operate together and attempt sybil you off the network by only giving you IP's controlled by them, but it is only one method used and it's only used during the initial set up of a node. The IP's are also sent over DNS, which gets cached by various DNS servers, making it nearly impossible to do that. After your node gets an initial list of node IPs your node keeps a DB of IP's and nodes share IP's between each other. The risk of an attack this way is absolutely tiny that its not even worth mentioning. As long as your node discovers the IP of one honest node, you are safe.

So is the vSeeds above necessary? What is x1, x5,x9 and xd anyway?