DAnti-Cheat System

[.kju 3244]

nice one

PS: @proper addons will be signed in the next days..

[Mr Groch 0]

How to send globalChat message to all players using dooacsInitScript?

Now when I use:

dooacsInitScript = "player globalchat """"Ble Ble""""";

Only connecting player will see that message...

[Doolittle 0]

That's only run when people connect. It's not meant for global chat.

[XaRaBaS 0]

I've send you a PM..

Ty

[Doolittle 0]

Since it seems the bad guys have the latest DooACS I'm going to post it up here. This is what I've been mailing out to a super-secret mailing list: dooacs5.zip.

This will detect all public cheats out there but will not be able to do anything with stopping the .EXE cheats.

For future releases I don't know what I'll do. Maybe go through list of people and see who the traitor was or if they allowed the file to be grabbed from their web server, etc. This also depends upon when cheat makers release a new version of their stupidity.

Doolittle

[brit~XR 0]

Make sure the guys you sending it to are who they say they are.

And dont send it to clans you dont no at all or trust as they could have a bunch of cheaters in there clan with ftp access to server

[Auss 208]

Damm shame Doolittle hang the arsewipe who gave it too them

[Doolittle 0]

I think they obtained it by nefarious means (intercepting the visible text net packet). But the good news is, now we know they know, so I can at least release the current version publicly. Also it's good to see they wanted to find DooACS... it means it bothered them. I just need to make sure it keeps bothering them when they release next cheat version.

Don't forget, their public cheat is still stopped by this. They haven't released a fix even though they have the source code. I dunno why. I guess they only have one programmer who's busy eating children?

[[aps]gnat 28]

Darn, this is where I'd hope you were going to say every mailed version had its own little tell-tail ..... so the leak was tracable.

.... little kiddies. Go hack some government server ffs, that way you might "disappear".

[Guest]

Sad to hear they gotten their hands on this but it was to be expected offcourse

Like you say it is good they wanted it so bad, your tool has been a relief in many games I played so far

@[APS]Gnat

Although I fully agree with you on the idea it might cause a lot more work and confusion for doolittle himself.

Maybe if he would have someone who could help him with that it might be a nice idea for the future.

And.....if it worked it would be nicely to publically hang the dude

[Dwarden 1125]

i think running this project as Open (Source) Community Project is now the best solution ...

sure they may see what You do and how ...

but with closed project there is risk of 'leaks' You don't know about at all

so it's easier to work with knowledge that they know same as You ...

[Doolittle 0]

That's a good point. I think they saw what I was doing by just checking the network traffic. But who knows. It's not important to find the "leak"... more important to help these cheater people with finding some morals. And if they have problems with that... then yeah, maybe people could assist in making this tool even better.

I'm open to talking about ways to make it better on here.

Doolittle

[Nutty_101 0]

Prolly sniffed the packets. That was way to simple to pull off as everything pops over in simple text.

Good job though. Least it kept the normal users at bay for a little bit.

[bluevein 0]

damn, i only just got this and has already been exploited.

oh well. I still haven't got it to work in my server yet

i don't know about making it public? I think that will lead to a quick fix for them! but I'ts good to know it's bothering them! lets just keep them bothered.

[LtCmdrBoon 0]

XAM 1.3 is blocked, but 1.4 is still getting through. I dont accuse the XAM guys of hacking, its just with 50+ players on the server, when they begin 2 show up, things start going wrong big time and the only thing to fix it is a reset of the server.

the doolittle has stopped several players a day attempting to connect with whatever it searches for, we still got the problem with AT's such as 136, being able to auto-target like the javelin can, but there isn't really a way to prove it, and unless I modify the bezerk and some admin is willing to be a godmode civi walking around the whole mission instead of playing, but idk what the limitations of a mod are, and anyone can create a mod, call it "best_sound_mod" and have it do whatever they want. ARGH

Signed mods work well, but with lots of players and some players now connecting with 10+ mods, it causes unplayable amounts of lag on this event.

[Doolittle 0]

You mean you used the dooacsDisabledPatches to kick XAM players?

[njmatrix 2]

what about starting a community listing that invests in non cheating clans and only play with these members . Also start passing along IP's to ban and once people start getting banned everywhere they will slow it down. I mean this wont stop everyone but it works for those of us who play Joint Operations (which was dropped by Punkbuster) It doesnt solve the problem but it greatly cuts it down

[[kh]jman 49]

You mean you used the dooacsDisabledPatches to kick XAM players?

Yes we have this in of server's .sqf file:

dacsDisabledPatches = "[""""XAM_classes""""]";

That presumably blocks XAM 1.3 but not as LtCmdrBoon says XAM1.4. Doolittle could you explain to us what file we need to identify in any mod/addon that can be added to the 'dacsDisabledPatches' variable to block a particular mod?

[Dwarden 1125]

should be

dooacsDisabledPatches = "[""""XAM_classes""""]";

for latest version

btw this messed anyone using XAM_GHIL (ghillies)

[[kh]jman 49]

Thanks Dwarden I couldn't see the wood for the trees

[Doolittle 0]

Unfortunately I don't know what CfgPatch name addon makers use and that's what I need you to go by.

How to find that info?? One way is for someone to be nice enough to depbo the XAM files and uncompress the config.bin file to config.cpp text and look for CfgPatches entry and get the name used. I downloaded XAM 1.3 and saw this was XAM_classes but haven't had a chance to grab 1.4 so maybe they changed that name.

Note there could be many CfgPatches in a particular addon. You just need to use one in dooacsDisabledPatches...

[[kh]jman 49]

For XAM 1.4 the CfgPatches entry is XAM_Markers thus the following will block XAM 1.3 & XAM 1.4

*EDITED

dooacsDisabledPatches = "[""""XAM_classes"""", """"XAM_Markers""""]";

Incidently I have the XAM Ghilies and that passes the dooacs check so that must use another name but I'm not going to extract the pbo's to find out what it is as I don't think that mod in itself will cause serverside issues.

[Doolittle 0]

Thanks for looking that up. Also, it should be:

<table border="0" align="center" width="95%" cellpadding="0" cellspacing="0"><tr><td>Code Sample </td></tr><tr><td id="CODE">dooacsDisabledPatches = "[""""XAM_classes"""", """"XAM_Markers""""]";

[Mr Groch 0]

I think that DooACS is disabling Extendent Eventhandlers on the server.

I want to use VFAI Smokeshell addon, that needs Extendent

Eventhandlers addon, and it is not working when DooACS is enabled.

It works fine, when I disable dooacs.pbo on the server...

(I'm talking about server side addons only)

[Dwarden 1125]

i can confirm this

i got several problems with XEH and EEH addons on dedicated server too while DOOACS was in place

since i removed them these issues are gone