[tHeWiZaRdOfDoS]

eMule.v0.47a - TOMBSTONE v1.48

Changelog:

CORE: ClientAnalyzer v1.4:
//v1.4:  14 changes
//-   Force one score calculation on startup
//-   New function "IsBadGuy()" - can be used to draw an icon or something...
//-   Made some functions non-static using the parent pointer
//-   Only use the UL/DL treshold as a punisher for clients that have something for us
//-   Fast Reask treshold will only be used after collecting 3 reasks
//-   XS spam/exploit check changed due to buggy implementation (***/WiZ)
//-   XS exploiters will only be checked after 10 reasks
//-   Punishment for Nick- and/or ModThieves reduced to 3*AT_MIDPUNISH
//-   Combined punishment for UDP-FNF and/or FileFakers
//-   Changed logging to an uniform standard
//-   Added a try/catch handler on exit because a crash was experienced there (still searching for the reason)
//-   Added missing initialisation for the badaction counter
//-   tweaked some functions to not call ReCheckScore() if it wasn't needed
//-   replaced the memset command by md4clr for the hashkey

Changelog v1.48:

- FIXED:  fixed some localization problems
- CHANGED:  default nickname changed
- CHANGED:  removed some unneeded codelines in modstring sort
- FIXED:  fixed the display for remaining size (added a separate column to upload)
- REMOVED:  min upload for trickle slots (system seems to work fine now), should fix the incorrect trickle slot number display, too


Changelog v1.47:

- FIXED:  fixed multiple instances checkbox display
- ADDED:  real full chunk upload plus remaining upload data display from SF-IOM mod - TAG: VQB: fullChunk
- CHANGED:  when slotfocus is enabled, then try to send at least 1k to trickles
- CHANGED:  slotopening again, takes into concern the number of trickle slots


Changelog v1.46:

- CHANGED:  changed the error dumping code to ALWAYS create the dump and to remember the user on startup,
   this should help in cases where no dumps were written - TAG: WiZaRd::Better dumping
- ADDED:  various code improvements to save CPU - TAG: WiZaRd::Save CPU
- CHANGED:  slotopening on both slotfocus and fixed datarate


Changelog v1.45:

- ADDED:  faster slotopening after UL session end
- ADDED:  firewalled retries limit (limit: 15 retries ~ 30 minutes)
- ADDED:  KAD-patch by Unkown1
- ADDED:  DynamicBlockRequests by Netfinity - TAG: NetFinity::DynamicBlockRequests


Changelog v1.44:

- CHANGED:  refined slotopening of slotfocus mode
- CHANGED:  small change in filescore calculation to save cpu
- ADDED:  cpu calm down on score calculation - TaG: WiZaRd::CPU calm down*
- FIXED:  added some codechanges to fix improperly counted failed ul/dl sessions

*I *think* that this was once introduced in a similar way by LoveLace... in this case: "idea by LoveLace"


Changelog v1.43:

- ADDED:  Startup Flood Prevention proposed by James R. Bath (http://forum.emule-project.net/index.php?showtopic=101181) - TAG: WiZaRd::Startup Flood Prevention
- ADDED:  dumpfile enumeration - TAG: WiZaRd::Dumpfile Enumeration
- ADDED:  automatic recheck firewalled status - TAG: WiZaRd::Automatic Firewalled Retries
- CHANGED:  try to connect to kad by default
- FIXED:  added a patch to multiple instances to prevent another instance to start when starting a new download (seems like an official bug to me)
- FIXED:  definately fixed the traytooltip to show up properly *g*
- CHANGED:  more comments in code... every b00n should be able to copy everything he wants now AND learn something *g*
- ADDED:  ModVersion display in all important columns - TAG: WiZaRd::Show ModVer
- CHANGED:  improved slotfocus slotopening a bit (less slots... at least I hope so *lol*)


Changelog v1.42:

- ADDED:  a "warning" popup on first start to inform the users of the purpose of the mod
- CHANGED:  if you are updating from a tombstone version then the "first time wizard" won't pop up - TAG: WiZaRd::NoWiZaRd (*rofl*)
- FIXED:  fixed the traytooltip to show up properly (who needs to know the version anyways... the speed is important;)) - TAG: WiZaRd::ToolTip-FiX
- CHANGED:  added some better tagging/comments to the code
- FIXED:	Glitch-FiX in CDownloadClientsCtrl.cpp - TAG: WiZaRd::Glitch-FiX [21.02.2006]
- CHANGED:  SlotFocus is active now by setting datarate to "0" (default)
//if slotfocus is active then a datarate of 10kB is used to determine the needed slots
- ADDED:  added a checkbox to enable/disable the allowance of multiple instances


Changelog v1.41:

- ADDED:  10sec delay before opening a new slot
- ADDED:  SlotFocus (fixed)
- ADDED:  datarate selection
- REMOVED:  possibility to switch off full chunk transfer
- FIXED:  additional icon display
- FIXED:  lang update was not working
- CHANGED:  CS-tree is now expanded by default
- CHANGED:  crash dump creation is always active


Changelog v1.40:

Based upon v0.47a:

- ADDED:  new splashscreen (+sig +avatar) by Mr.FrEEzEr - thx a lot!
- ADDED:  icon for badguys (SKULL)
- ADDED:  icon for same mod (TOMBSTONE) - TAG: WiZaRd::Same ModVersion Detection
- ADDED:  modversion - TAG: WiZaRd::Easy ModVersion
- FIXED:  BugFix in XS packet creation (Xtreme/***/WiZ)
- ADDED:  SessionRatio 1:4
- REMOVED:  SpamBan (due to the analyzer)
- CHANGED:  you can now select between 3 cs: none, official and analyzer (recommended+default)

Please do NOT use your old antileech.net files (from Xtreme based versions)



Download @ eMuleFuture.de








OLD VERSIONS:

TOMBSTONE v1.1

based upon "LeecherKiller" Xtreme v4.7.2

PLEASE MAKE A CLEANINSTALL!
NO hash - NO clients.met!
In any case delete the antileech.met file in your config folder!
This is to get more reliable and correct results in the stats - thx

Changelog:

added:  nickthief stats
added:  correct naming for leecher stats :)
added:  added a "reaskbuffer" to the analyzer reask score to only punish really fast reasks
added:  option to toggle the usage of the analyzer score - without that, you'll have an Xtreme WITHOUT banning/punishing + stats :)
fixed:  fixed a bug of mine in Xtremes modfaker detection (though I do not use that it was just cosmetical...)
fixed:  fixed one bug in scoring which I merged from an older version :( 
fixed:  really removed the "scorereduce without justice" of Xtreme

TOMBSTONE v1.0

Changelog:

removed:  Xman splash and replaced by the default mechanism
removed:  removed ALL bans of Xtreme mods "DLP" (= Dumb Leecher Protection) because
    most of them are nonsense and the scorereduce because it's highly unfair
changed:  changed the code around ProcessMessage to only show a logline if a received msg was not filtered
added:	stats for UL/DL for the detected leechertypes
added:	CLIENTANALYZER

After watching how current antileecherlists grow and grow banning more and more unguilty guys just because of strange modnames, I thought it'd be wise to start a new project... first, I wanted to rally some modders to join me in coding but then it turned out that they were either in the denial ("such a system is not possible") or in waiting ("code it and then I will check it out") state or willing to help but lacking the skills to do so...
So the CLIENTANALYZER is a beta project of mine to detect and punish leechers by analyzing their behaviour towards YOU only!
That means a client that is behaving bad to us but good to others will be punished by us only
even if his name is "Super-Leecher-0-Upload-User" and he uses a mod like "One hell of a leech mod"
I don't think it's ok to ban/punish clients just because of nick/modname/ghosting or modding errors...
If that does not hurt me, why should I punish them? Nearly all "bad" mods can be used without
the bad features activated...

Please note - ALL code is beta, ALL values might be changed easily, nothing HAS to stay as it is right now...
I'm open to all critics and would be glad to hear some suggestions and reports!

You can either enable the official CS or disable it - the analyzer will always be active!
If enabled and a client has an official score of *10 and an analyzer score of *0.2 then his complete score will be 10*0.2=*2
else his score will be *0.2!

The mod currently gives a score of *1.0 for all clients by default which won't change anything...
A really bad client (xs-exploiter/filefaker/modthief/nickthief) will get a reduce of 50%
Clients will get a bonus/punisher for uploaded/downloaded data, though, only data > 80% of a chunk will be counted
Uploaded/Downloaded data will be weighted differently
Every spam message received will lower a clients score by 2.5%
Clients who reask too fast or send XS too fast will be punished



More infos from the code comments:

//////////////////////////////////////////////////////////////////////////
//About ClientAnalyzer:
//---------------------
//The purpose of this class is to provide an interface that is controlling all
//kinds of clients actions in eMule and to provide a score determined by the actions of each client
//That way, Modders won't need to update a "antileech" database file regularly with
//strings/opcodes or other things that are loose guesses about a client but just implement
//that class so leechers will be detected by their ACTIONS
//
//
//A few examples:
//---------------
//
//A releaser uses a mod with kick/ban/PS on partfiles and so on - would/should you ban him?
//Yes you WOULD with default methods but no, you SHOULD not ban that client!
//He is RELEASING, he is supporting the network and increasing its health...
//But as you can't destinguish between "good" clients using that mod (aka releases)
//and "bad" clients using the same mod (aka leechers) you would ban him/punish him on sight
//(though the latter should be forbidden iMHO - still waiting for a statement by the devs)
//
//A client uses a leecher mod by a modder with a brain of > half the size of a walnut,
//which means he won't send a string/opcode/something to identify himself - what to do?
//Default methods fail miserably in such cases... and the default CS is too exploitable
//
//A client uses a leecher mod which spams the network - what to do?
//Using default methods you are required to release a new filterfile over and over again...
//The class will use the user editable blocklist and remember good and bad messages automatically
//
//
//So, a final conclusion:
//-----------------------
//The class will NOT (NEVER!) need any updates in its final state!
//The class will AUTOMATICALLY collect and use data from each client!
//The class will REMEMBER that data and store it in a antileech.met file!
//The class will work ONLY by analyzing the BEHAVIOUR of a client to us!
//That means it is ABSOLUTELY following the rules and maybe even worth to be used officially!
//
//////////////////////////////////////////////////////////////////////////

Download


Have phun! Find the leechers and don't ban'em too fast!
WiZaRd

This post has been edited by tHeWiZaRdOfDoS: 15 March 2006 - 05:17 PM

[Anabolic-Frolic]

I will chance it.
Nice Pic, but not the Undertaker...

thx

This post has been edited by Anabolic-Frolic: 27 November 2005 - 10:36 PM

[lordpake]

Nice pic indeed, tempts me to test this mod (lol)

[tHeWiZaRdOfDoS]

*lol* - well, 2 good arguments are always better than one *g

Important addition: you can set whatever you want (ban/score reduce) - it will ALWAYS be deactivated because it's just logging the bans and evaluating the data...
This is just a quick-merge of my code to Xtreme codebase to collect data about how reasonable the bannings are and about how effective (if at all) the analyzer works

[bounty vb]

this should be interesting, i'll try it

[Ingolf]

Great idea about punishment instead of banning! I will surdenly try it out!

The MOD name should be Xtreme Punisher, since that pic keeps jumping into my head whenever you refer to 'punishment'.

[Stulle]

without having read the first post completly I think this is pure nonsense!

this version doesn't have to be released in order to test something! you can search for some well chosen testers in order to test something.

this release has just one purpose: revenge!
WTF is the matter here¿ are you kinda pissed cause there are people indeed working different but you¿ When will there be a "Tombstone" based on Onyxmule which uses reduce score, as well¿

and the bad polemic about "DLP" is just awfully childish! You don't like the system DavidXanatos introduced and I agree with you about this but now trying to piss off Xman 'cause he made his own system... come on, how old are you¿

I recommend to stop the whole discussion right now untill there is an official statement. Unless there ain't any statement by the devs it's just stupid polemic like Mr. Fischer loves/ loved to use and a discussion running in circles. This is even worse but my little fight with Tuxman since way better coders are involved and way better coders are pissing off each other which does NOT help the community!

With kind regards
Stulle

[tHeWiZaRdOfDoS]

Heyho cool down Stulle
I used XTreme codebase simply because it has the most so-called "Anti-Leecher-Features" included up2now and it's pretty easy to change it so it will only detect them and fill the stats without banning them so this should be pretty interesting...


I'd loved to write this thing with the help of Xman but he was one the modders in "denial" state... just a pity...


Concerning the "war"... well, I heard from about 4 different sources that Xman started to collect information about me and to blame me for leeching/modding leecher mods and so on... so if - at all - there is someone you want to complain, drop him a line

[Stulle]

tHeWiZaRdOfDoS, on Nov 27 2005, 11:20 PM, said:

Heyho cool down Stulle
I used XTreme codebase simply because it has the most so-called "Anti-Leecher-Features" included up2now and it's pretty easy to change it so it will only detect them and fill the stats without banning them so this should be pretty interesting...


I'd loved to write this thing with the help of Xman but he was one the modders in "denial" state... just a pity...


Concerning the "war"... well, I heard from about 4 different sources that Xman started to collect information about me and to blame me for leeching/modding leecher mods and so on... so if - at all - there is someone you want to complain, drop him a line

oh come on, don't pretend to be an angel! this whole story started at kademlia-net, continued in the ghost mod thread here and have a look where we are now.

this is so redicoulus. and all this just because he don't like your anti-leech system¿
oh and btw, most of the mechanisms in the Xtreme are either based on your systems or even simple recodes of your systems. what is so wrong about that¿

and please don't pretend to have chosen the Xtreme as the base of your so called test 'cause it had most mechanisms... your polemic showed us something else.

anyways, all you said didn't change the slightest detail about the fact you made a SOOOOOO public test... if I'm not totally wrong your DaRkMaGiC betas does have a time limit... should one make think about your intentions in this topic...

With kind regards
Stulle

[tHeWiZaRdOfDoS]

I really don't get your point, maybe I'm too tired already... however, I hope to gain valuable data from the testers here about the leechertypes and so on...
Concerning the Xtreme ban-mechanisms they are just that: xtreme! There are LOTS of mechanisms in there (e.g. Anti-Ghost-Mod) which do NOT evaluate behaviour but just "ban on sight" and that's what my code and philosophy is totally against...

Let's go to bed for now and continue tomorrow...


... and happy testing to all nightfliers

[xscarab]

I've just run this and found this in the server log:

27/11/2005 23:18:13: Credit file loaded, 16608 clients are known, 92 clients deleted (not seen within 5 month)
27/11/2005 23:18:20: Error: AntiLeechFile is corrupted and will be replaced!

I transferred my crypt/pref/client files - it didn't like the clients.met?

Also it's been running about 20 mins now and has so far only found 14 sources out of the approx 120 available for the only download i have.

[Xman1]

@Wizard
If you don't remove this mod from all boards until the next 12 hours, I'll report a rule violation and include it to my ban list.

reason:
this mod has many bad featues and is using a file-trading-system. What this mod doesn't do: punishing any leecher.

I can understand your intention to fight against Xtreme.... it is the firt mod, which detects your leechermods, you want to earn money with.

I give you the alternatives:
- build better leechers which I can't detect and stop fighting against Xtreme
- stop coding leechers and fight with me (and many others) against leechers.

regards
Xman

[wolf_79]

DDoS Mirror Updated:
Binaries

Sources

Thx tHeWiZaRdOfDoS

[seppl12]

Wiz said:

You can either enable the official CS or disable it - the analyzer will always be active!
If enabled and a client has an official score of *10 and an analyzer score of *0.2 then his complete score will be 10*0.2=*2
else his score will be *0.2!

There is a fault in your thinking. If a good client has an official score of 10 than he has a difference of chunks down-up of abaut 9. Your score, i called it Wiz-score, is (initial by 1.0):

Wiz-score: cur_score += (chunksDL - chunksUL) * (100/1000) = 1.9

Thus the result score is: 10 * 1.9 = 19

Otherwise, is the difference of chunks e.g. -5 than the Wiz-score ist 0.5 and the result score also 0.5 (in the official is the lowest one 1.0).

I think, is not allowed because for the danger of trading.

This post has been edited by seppl12: 28 November 2005 - 02:24 AM

[alpdruck]

Xman1, on Nov 28 2005, 01:55 AM, said:

@Wizard
If you don't remove this mod from all boards until the next 12 hours, I'll report a rule violation and include it to my ban list.

reason:
this mod has many bad featues and is using a file-trading-system. What this mod doesn't do: punishing any leecher.

I can understand your intention to fight against Xtreme.... it is the firt mod, which detects your leechermods, you want to earn money with.

I give you the alternatives:
- build better leechers which I can't detect and stop fighting against Xtreme
- stop coding leechers and fight with me (and many others) against leechers.

regards
Xman

"many bad features"? Which exactly? The only ADDED feature is the clientanalyzer which modifies the creditsystem. All other features are from your very own mod.

[CiccioBastardo]

Despite your "interna war", I find this approach quite good.
And it satisfies the official request to punish clients by their behaviour. Yet, it still miss the network-overhead mods, but it is a good start.
I'll have a look at it ASAP.

@Xman
the fact that you can detect what you think are "leechers"is not a reason, not a jutification to ban them on sight.
I don't care about your issue with Wizard, I just think that your approach to the problem is wrong.
You may agree that the "Anti ghost" thing is really "stupid" when a mod can circumvent it with a "random" (and with this you know what I mean) modstring, if that is all you want. Do you want to keep a table of what mod implements which extension to know if official Morph uses a partcular extension? If not, well, you already have found the weak point in your system. If so, you are still limiting your system to the mod you know. So my "provocation" to ban all mods but those presented here sounds somehow fairer.
The conclusion of this is that I think your approach is wrong both ethically and technically. Were it working you would be unfair. But it is also not good (you may think it is now, but wait next version of those leecher mods!). A different approach is really needed. And this pecific proposal is ethically correct. Let's just see it is so also by a technically point of view.

No offense intended. I'm just expressing my thoughts on the subject.

[Ingolf]

Wowa! Bad karma already

I really do not hope there is a time limit on your mod wiz, and if you or others expect to make any money on the P2P idea, i would say you have completely misunderstood the whole P2P concept from the beginning

I have read several of your posts in the dev sections wiz, and i usually find your ideas, and suggestions to be good.. despite other ppl's/dev's rude behaviour. This is why i have a hard time swallowing this up in a flash... i will still test your mod, when i get back home

[Xman1]

@CiccioBastardo
first one last note about ghost-mods:
of course they can use a wrong modstring, like morph (not xtreme.. i would detect this). But with doing this they advertise morph... and thats something they don't like.
About my other detection systems:
they work! And they don't ban any of the "legal" mods. Not from this board, not from any other board.
about this mod:
pealse first check out the sources.. and find out how bad this mod is. Beside it is bad from its features.. it's full of bugs.

[CiccioBastardo]

I'll check it, and don't worry, I'll report anything I won't like either

[alpdruck]

Xman1, on Nov 28 2005, 12:00 PM, said:

@CiccioBastardo
first one last note about ghost-mods:
of course they can use a wrong modstring, like morph (not xtreme.. i would detect this). But with doing this they advertise morph... and thats something they don't like.
About my other detection systems:
they work! And they don't ban any of the "legal" mods. Not from this board, not from any other board.
about this mod:
pealse first check out the sources.. and find out how bad this mod is. Beside it is bad from its features.. it's full of bugs.

Again you say "bad features" and "full of bugs" without actually stating what is bad and what is buggy. Why don't you say what the specific problems are?