|
Title: Ip from Segwit2x malicious nodes Post by: chek2fire on October 23, 2017, 06:49:10 PM Here is the list of the current nodes that support segwit2x hijack malicious fork
https://pastebin.com/iEyasvay I will update it every Monday and Thursday with a new message in this topic. I advice everyone that run a bitcoin node to ban this nodes asap. And here is the script for everyone that run a node and want to ban this malicious nodes. https://github.com/mariodian/ban-segshit8x-nodes Bitcoin FTW! Title: Re: Ip from Segwit2x malicious nodes Post by: .anto. on November 06, 2017, 09:59:17 AM Here is the list of the current nodes that support segwit2x hijack malicious fork https://pastebin.com/iEyasvay I assume there are a lot more IP addresses of the nodes supporting segwit2x by now. Is this list of that IP addreses up to date? My 2 nodes have been on Bitcoin Core 0.15.0.1 since last month. But after the implementation of the disguise feature on this commit (https://github.com/btc1/bitcoin/commit/28ebbdb1f4ab632a1500b2c412a157839608fed0), I am not sure anymore how to ban the nodes running with that codes. I don't like the idea of this hard fork, so I don't want to let my nodes listen and propagate those nodes to the network. Title: Re: Ip from Segwit2x malicious nodes Post by: chek2fire on November 06, 2017, 12:12:11 PM is not upto date but is very difficult to create a new list without the previous ip. I have yesteday the script and it was 1917 segwit2x nodes. The best thing is everyone to download this script and run it manual.
Title: Re: Ip from Segwit2x malicious nodes Post by: .anto. on November 06, 2017, 01:05:17 PM How did you collect those IP addresses?
I have implemented a quick and dirty workaround to block the nodes that I thought bad ones as I explained on this post (https://bitcointalk.org/index.php?topic=1371683.0). I am using a script to collect the IP addresses from the debug.log based on certain criteria, and I use iptables and ipset to block them accessing my nodes at my firewall. Bitcoin Core 0.15.0.1 does that kind of banning smartly at protocol level for the segwit2x nodes. But now, since the disguise feature was implemented, I am not sure what kind of criteria that we can implement at user level, to collect the IP addresses of those segwit2x nodes which use that feature. Does anybody else have any suggestions? Title: Re: Ip from Segwit2x malicious nodes Post by: chek2fire on November 06, 2017, 01:35:33 PM How did you collect those IP addresses? I have implemented a quick and dirty workaround to block the nodes that I thought bad ones as I explained on this post (https://bitcointalk.org/index.php?topic=1371683.0). I am using a script to collect the IP addresses from the debug.log based on certain criteria, and I use iptables and ipset to block them accessing my nodes at my firewall. Bitcoin Core 0.15.0.1 does that kind of banning smartly at protocol level for the segwit2x nodes. But now, since the disguise feature was implemented, I am not sure what kind of criteria that we can implement at user level, to collect the IP addresses of those segwit2x nodes which use that feature. Does anybody else have any suggestions? when you run the script in terminal you see and the ip that banned. The problem is that if you run it again it show them again the new and the old ones |