[AndCycle]

due to the recent incident,

one of the biggest subtitles website in China, shooter.cn have been taken down,
someone made a huge package around 73GB total backup of those subtitles spread on ed2k,

unfortunately this seems the primary target of those fake client,

fake client simply keep sending out highly compressed garbage that make emule busy on hashing corrupt data,
which is so efficient because there is no builtin solution to protect against this attack,
and emule have serious locking issue while hashing makes GUI with no response,

this literally paralyzed my aged emule,

anyone interested in getting doomed, search "shooter.zip(ED2000.COM).001"

[coluche]

Hm,

I can not test that file - I do not have 73 GB of free disc-space.

Maybe it is because I use a Mod with the Nice-Hash feature (set to 40%) that hashing for me never results in eMule-GUI freeze ? (more importantly - no freezes for other programs unless they also want to heavily use the HD)
((Here the OS is windows 7, and it deals still as appallingly as win98-or-so with conflicting HD-access.))

I do have eMule-GUI freezes from time to time, but I think it is more to do with when eMule wants to write to the harddisk (also : allocate disc-space), but the harddisk is busy from other processes. Or maybe even from eMule's diskwriting itself, like needing to allocate space for several files "at once".

Checking "Allocate full size for non-sparse part files" (options/ extended) might help with the latter, I don't know.

PS - can't you "ban" the corrupting client(s) by adding their IP to the IP-filter ?

This post has been edited by coluche: 18 December 2014 - 08:56 PM

[AndCycle]

fake client can easily make you start to hash useless garbage in seconds that take all your i/o resource,
because those fake data only take few kb to transfer one 9.28mb chunk,

allocate full file won't help because it simply force emule to
write out data, hashing, find out it's wrong, trying ICH to recover something if there is any, abandoned data,
this require a complete separate thread to work or it just lock your emule GUI until it's done,

about ban it,
first, normal emule mod won't show client ip,
second, I am pretty sure those client not on known ipfilter list,
and ip is not an issue for them, they got plenty, blacklist won't work for long,

in the end,
I just add few line of code the check packet unzip to see if there is any abnormal compression ratio then ban that client.