Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Kry]

But it is retarded. Flawed is when something is not working as intended, this is working as intended. It just so happens that the intention is retarded.

[Kry]

Also stulle knows me anyway HELLO STULLE.

[Stulle]

Hi Kry, hi others,

I am aware of this flaw and so was Xman, who originally added this code to his DLP. He added it though to fight the AJ community. Now, like I said on the official eMule board, we might as well remove this code because i doubt there are many clients left that still use that technique to identify themselves. I will wait for some feedback from you and others on this idea and will then probably remove that code for future versions or if possible remove it from the DLP - I don't got it up me brains just now - and release a new version of that.

Greetings,
Stulle

PS: Kry, you're always hilarious!

[Olhado]

Yay

I feel like I've been falsely accused and now I have a chance to fight for justice

[Stulle]

just to make sure everybody notices: i have released a new version of the DLP that removes the mentioned detection. i will subsequently - although probably nowhere really soon - remove the detection from MorphXT and StulleMule. clients using the DLP may simply update the Antileech.dll and make use of this change.

[wuischke]

Stulle: Thanks for reacting so fast and being very constructive about the matter, I appreciate this.

Do you know if there are other checks with a high false positives rate in the code? I assume you know the code best, but could you please have another look? Thanks in advance.

[Olhado]

I have set great events in motion

Thanks

[Stulle]

in fact i do not know that code very well. my only real contribution to the dlp is getting it released and doing the release build, all the rest is done by zz_fly - who took over the Xtreme project where Xman left it - and some of his contributors. the only reason i am taking care of the releases is that i am the only one with access to the SourceForge file release system for the eMule Xtreme project.

anyhow, i am positive that no other heuristic code will cause random clients to be punished without real reasons. there is some heuristic on random modstrings - which will probably only falsely trigger if somebody considers a random modstring to be the best name for his mod - and on HEX nick addons. the latter is again fairly safe because randomly adding HEX codes to the nick or making the nick entirely HEX is fairly stupid and seldome, imo.

keep in mind, i am not exactly familiar with all the heuristics and whatever detections. i am just writing from what i recall about it. if you want to be certain please review the code yourself and bring it up to me. when you want to bring something up please do it in a place i usually visit like emule-project so i won't miss it.

oh and about being swift with this, you're just lucky i am currently doing some coding and zz_fly had already done some work on the DLP or else it might have taken a lot longer. ;-)

[Stu Redman]

Stulle, thank you for fixing it so quick ly!