hello sharers ...
ElChele, on Nov 3 2007, 08:38 PM, said:
03/11/2007 20:00:13: 66.90.73.253 (66.90.73.253:6543) appears to be dead.
TCP port# is not 6543, but 8899.
host is online and seems to work fine.
Quote
I disagree, because I've this line:
212.179.18.129 - 212.179.18.144 , 90 , [L1]fake emule servers,[FK]4232-BezeqInterna,[FK]IL-BEZEQ-INTERNATION,
in my IPFilter.dat.
i disagree me too.
perhaps my ipfilter.dat is not up to date (

) or it's not the bluetack version.
I'll check that ...
but, if bluetack include a full ip range in the ipfilter.dat, because of some bad server(s) found onto, then, others servers online on same ip range will be unavailable for the ipfilter.dat users. it's already the case for some of 'good' US hosted servers.
If, for the example, MD publish some faked/spy servers in the same ip range of each 'good' servers, then, all eDonkey servers will be unavailable for the ipfilter.dat users ... So why bluetack (or other ipfilter producers) put an entire ip range and not only the specific IP of one bad server ? what is the 'server tests protocole' to classify a server as bad, or good .. ?
ipfilter users seems very paranoid, but not really protected.
the danger don't coming with servers, but with other bad spyer clients ...
i don't think the digital cops use servers to trap the users, but they find them with a modified client (thank to open source concept ...), by using a 'good' servers list, as gruk or peerates lists, and from a standard ISP dynamic IP address.
and its maintenance is not very easy, but heavy because the contents is very big and very hard to control.
i think perhaps more of 50% of ipfilter.dat content is unuseful...
At the end, ipfilter seems given a very low level of protection, but set an big black hole in the net map viewed by the client.
bye.