Need good Anti-FakeShare/Slot script
 

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

Need good Anti-FakeShare/Slot script

Started by grizli, 11 October, 2004, 17:43:41

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

grizli

Hi all,
I have so much problems with people fake sharing... is there anyway to prevent that??? They also faking number of slots.

BoJlk

Hi there!

Use DCDM++ for Fakers Problem...
And if you use RoboCop, then Set max Slots check.

ARCHANGEL

Use a client, not a script or scripts. Get yourself DCDM++, you'll find a link in the links section.

grizli

No, I have my own HUB. And the problem is with users.
I use RCv9.0 - Slot checker is on. Solved.
But DCMC++ doesn't do anything against fake shares... people trick it all the time.

BoJlk

#4
FakeShare cannot be solved :(
Because even scripts or DCDM check for particular File Size (the impossible one)

So, the only way is Checking Manually...
Banning the *** F***ers :)

I use Script For FakeShare Checking (it won't Help)

--Made by someone I don't remember who...
--Edited and Optimized by piglja - 11.03.03

badShare = { "10000000000","5368709120","10737418240","13630010000","16106127360",
"21474836480","26843545600","27000000000","32212254720","7970010000",
"37580963840","37970010000","6599201000000","65992010000000","36772010000000",
"3677201000000","42949672960","48318382080","214266156265","53687091200",
"59055800320","1747201000000","16772010000000","147720100000000","10240000000000",
"64424509440","65719010000","69793218560","75161927680","80530636800","85899345920",
"91268055040","96636764160","102005473280","102400000000","107374182400","118648471552",
"128849018880","140301549174","161061273600","174720100000","183287729356","214748364800",
"268435456000","322122547200","375809638400","397760100000","429496729600","536870912000",
"657190100000","1024000000000","183287729357","102392020337","13625783747","174719269601",
"65712999629","26993869455","140295106724","199715979264" }

function checkFake(user)
local s, e, shared = strfind(user.sMyInfoString, "$ALL %S+ .-$ $.+.$.-$(%d+)")
return foreachi(badShare, function(id, value) if value == %shared then return id end end)
end

function NewUserConnected(user)
	if checkFake(user) then user:SendData("*** You seem to be using a fakeshare client") 
	user:Disconnect() 
    end
end

function OpConnected(user)
	if checkFake(user) then user:SendData("*** You seem to be using a fakeshare client") 
	user:Disconnect() 
    end
end

The impossible FileSize i mean like 128849018880 bytes, is not a valid file size...thou Fakers Can Modify the Files they Fake to get thru...

I've Posted the Same Thread some time ago...
So you should check him too Click Here to go to the Thread >>

bastya_elvtars

its the 1st time i hear that dcdm++ cannot detect any intentionally faked share...
Everything could have been anything else and it would have just as much meaning.

BoJlk

I might be wrong about the DCDM++

Herodes

the fake share problem cannot be not even 95% solved ...

as plop said ..

any share size can be faked ...

bastya_elvtars

please understand it for good:


This is Direct Connect,


so you cannot rely on a serverside thing as the same amount or more things happen in client-client communication, which is hard and incomplete 4 the server 2 retrieve...

so thats why dc++k cdm was born, then dcdm (and ofcourse others) - cause the server partially knows what goes on between clients, its the best way 2 use a CLIENT  for such purposes... We are not lazy to make scripts, but its twice bad if we make a fake finder: it just finds atoms of real fakers, and we waste a lot of time on it :D
Everything could have been anything else and it would have just as much meaning.

grizli

Ok, I guess people just gonna keep on doing it  :(

SMF spam blocked by CleanTalk