Ban people using whoisRI
 

News:

29 December 2022 - PtokaX 0.5.3.0 (20th anniversary edition) released...
11 April 2017 - PtokaX 0.5.2.2 released...
8 April 2015 Anti child and anti pedo pr0n scripts are not allowed anymore on this board!
28 September 2015 - PtokaX 0.5.2.1 for Windows 10 IoT released...
3 September 2015 - PtokaX 0.5.2.1 released...
16 August 2015 - PtokaX 0.5.2.0 released...
1 August 2015 - Crowdfunding for ADC protocol support in PtokaX ended. Clearly nobody want ADC support...
30 June 2015 - PtokaX 0.5.1.0 released...
30 April 2015 Crowdfunding for ADC protocol support in PtokaX
26 April 2015 New support hub!
20 February 2015 - PtokaX 0.5.0.3 released...
13 April 2014 - PtokaX 0.5.0.2 released...
23 March 2014 - PtokaX testing version 0.5.0.1 build 454 is available.
04 March 2014 - PtokaX.org sites were temporary down because of DDOS attacks and issues with hosting service provider.

Main Menu

Ban people using whoisRI

Started by blackwings, 03 June, 2004, 01:29:31

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

blackwings

Heh, this is just some crazy idea I got from checking the SL bot by Chill. It seems like No matter what your IP is(and ofcourse you don't change ISP), the information you get(or some useful information) from useing the +whoisRi command in SL, can it be possible to use this information to ban/block a user forever?

If you people start to say it's impossible, then how about this idea =

When a user connect, the command(or the function it is doing) +whoisRI is runned automatically and the information is saved to a text file and from this text file the the script look for a certain information, if this information is found and match a information in another text/dat file, then the user will get disconnected.

Anyway, if it would be possible, this would be a great way to keep away some of the worst fakers and rule breaker even if they change their IP.


tezlo

sure it's possible.. but requesting the info on every new user may cause some serious lag
plus.. you want to ban the whole ISP because of one faker?
or what other information did you have in mind?

blackwings

#2
QuoteOriginally posted by tezlo
sure it's possible.. but requesting the info on every new user may cause some serious lag
plus.. you want to ban the whole ISP because of one faker?
or what other information did you have in mind?

I had in mind to block a single user(or serveral if there are more fakers I want to block), not the whole ISP.
But I don't think it's a problem with the bandwith for me, I have 10Mbit internet and my hub is small, so I will be ok.

So it would be really nice if someone could make a script which could do this :)


blackwings

Please, could anyone try to make a script like this? I would be very grateful if someone did it :)


nErBoS

Hi,

For banning the faker like you want you will banned the a whole ISP range and thats is not fair to other users that aren't fakers and are using the same ISP. Mots of the IPS are always changing IP of the users then the faker could be entering with a different IP.

Best regards, nErBoS
--## nErBoS Spot ##--

Metaphase

Mac address banning would be a good idea but even then Mac addresses can be cloned.

SaintSinner

QuoteOriginally posted by Metaphase
Mac address banning would be a good idea but even then Mac addresses can be cloned.

Yup I agree, unfortunatly you will never know a persons Mac address...(its not transmited with ip)

Now I do think there are trojans that can accomplish this but we dont want to be looking into that now do we?
   


Shurlock

#7
QuoteOriginally posted by blackwings
Please, could anyone try to make a script like this? I would be very grateful if someone did it :)

OK, I know that the following is not a 'guaranteed' way to block that one user, but it's an option.

I use DC++k CMD along with the normal DC++ to check clients and 'forbidden files'.
Should I encounter a user that I very much dislike entering the hub, I use the following procedure with acceptable results.

I check the filelist of that user for any  file or folder that has a 'specific' misspelling or marking. Nearly every user has such a file or folder.

All I have to do is place that info as a forbidden file in ADL-Search and have CMD kick that user for the forbidden file.
Worst case scenario is that some user might have copied the exact same thing. Well, that I believe to be acceptable. Not  acceptable would be (as said earlier) is blocking an IP range due to one person.
If it's raining and your roof leaks, fix the roof. DON'T try to stop the rain!!

SMF spam blocked by CleanTalk