Deal with multiple (clone) self-registrations.

[Mardeg]

Registered clone detection should consist of:

1st number in IP, eg: 217.xxx.xxx.xxx

   AND

identical (password) OR (sharesize) OR (email - only when one exists) OR (description - only when one exists)

stored in an external file and automatically checked against when users register, also a manual check command on individual users should be available.

Options to do one of the following: prevent registration and notify user to login with their original nick, allow registration but demote to ChatOnly level, and lastly (for worst offenders) allow registration but add to silent Leecher list. (Last two would block $ConnectToMe)

Nickban and IP ban would be pretty much useless on users already employing evasion tactics.

Possible option to match identical IP number, but it might hurt users sharing an IP or by chance being allocated the same dynamic IPs at different times.

[n1ck]

a 'bit' off topic - but you raised a good point, what are the possiblities of a user being banned because he/she has picked up a dynamic address you have already banned?
 I always thought it was very remote??

[Mardeg]

Well I guess the worst offenders always seem to be able to change their IPs easily, and my thoughts are not so much that an innocent user would find their IP banned, but that such behaviour by offenders makes the permanent individual IP ban useless in the first place, hence the "profile matching" method I suggested.
Tempbans are fine though and could be incorporated into it if need be.

The point is to cut down on the many users registering multiple nicks for various reasons, more often than not to avoid being detected as a leecher not sharing what they download when you want to compare their filelist to the entries for their nick in Uploads.log

[b_w_johan]

Deal with multiple (clone) self-registrations.

ok thats anoying when 1 person enters with 3 clients.
what if 3 persons enter with 1 client each ??

Registered clone detection should consist of:

1st number in IP, eg: 217.xxx.xxx.xxx

....
ok my IP
217.0.0.1
my brothers IP
217.0.0.1
my dads IP
217.0.0.1
....

so first of all you want to ban on IP wich is dubbel in there ????


identical (password) OR (sharesize) OR (email - only when one exists) OR (description - only when one exists)
so everybody without discription or without email is banned,
in my hub there are say if there are 100 users 60 people haven't got a discription so those are duplicated.
the other 40 don't have an email set... so also duplcated ban also

i know 3 users in my hub with this password...
654321
3 other users to be banned ...
automatically banning on such things is meaningless..

yust manually check the IPs or make a script wich sends in OPchat all info about 2 users with same IP
like nick, pass, client,discription,email adress..
if you don't trust it you can send those 2 an email
asking why he is connecting with 2 clients on 1 IP cause routers do exist and users who arent origional to read example with password..

[Mardeg]

Please. You severely misunderstood the request. You proved you misunderstood it by leaving out the

AND

In other words, the detection REQUIRES the first number of the IP *AND* at least an exact match of one of the other things. The chances of more than one person having the same password in the same 217.x.x.x are remote enough for this to work, especially if your script already prevents "numbers only" passwords, aswell as other "easily guessable" words.

The script should ONLY check matching emails or descriptions if they exist, it is NOT meant to ban users without them. If they don't exist then only the sharesize and password are available for matching.

Also about the banning, the request was for something OTHER than banning to be done upon a match. Please read it MUCH more carefully before commenting.