problems with anticheat

Spark2 · Post by **Spark2** » Mon Apr 19, 2004 2:41 am

The /cheaters output is
0 [|Spark] [4233E58271411FA652152CE433E1A6AB10D6E0B0] [clean linux]
if that helps.

Spark2 · Post by **Spark2** » Mon Apr 19, 2004 2:42 am

Fedora Core 1 with many custom packages (but no custom kernel).
kernel-2.4.22-1.2115.nptl
glibc-2.3.3-12

Post by **bani** » Mon Apr 19, 2004 2:44 am

can you connect to the quaketheism server so I can get a log?

69.93.136.70:27969

Spark2 · Post by **Spark2** » Mon Apr 19, 2004 2:52 am

Done.

l30 · Post by **l30** » Mon Apr 19, 2004 9:38 am

Spark2 wrote:The /cheaters output is
0 [|Spark] [4233E58271411FA652152CE433E1A6AB10D6E0B0] [clean linux]
if that helps.

Isn't he a clean client?

zinx · Post by **zinx** » Wed Apr 21, 2004 11:31 am

Spark2 wrote:Fedora Core 1 with many custom packages (but no custom kernel).
kernel-2.4.22-1.2115.nptl
glibc-2.3.3-12

Can you send me the .rpm you're using for glibc 2.3.3-12, or verify that glibc 2.3.3-20 has the same problem?

Spark2 · Post by **Spark2** » Thu Apr 22, 2004 4:29 pm

Yes, upgraded to rev 20 and still get reported as cheating (just got kicked again by friendly admins...).

Linux Rookie · Post by **Linux Rookie** » Fri Apr 23, 2004 1:52 am

I have the same problem with Fedora Core 1.91 running with the 2.6.1-1.65 kernel, glibc version 2.3.3-17 running nvidia graphic card drivers. I have been banned from the BBC server kicked from several other servers in the past week. I have deleted all files and reinstalled but no matter what I do I get called a cheater, I see no warnings on my screen and typing /cheaters
it says I am clean.

zinx · Post by **zinx** » Fri Apr 23, 2004 9:44 am

The false positives on Fedora have been fixed in the development cgame

Lekdevil.NL · Post by **Lekdevil.NL** » Fri Apr 23, 2004 12:01 pm

Just curious: how do you guys plan to handle any false positives in the future? As the ETPro anticheat does not have any auto-update feature (yet?), does that mean that all updates need to be installed manually by all server admins?

Any form of anticheat that relies on stale, static data will be out-of-date the moment it is released. Not wanting to be overly pessimistic, but these types of anticheat systems have been tried in the past and failed. Either because updates don't get installed and cheats remain undetected because of that, or because false positives don't get nixed, thereby reducing the confidence level of the system as a whole.

Any comments on that?

Thanks.

Post by **bani** » Fri Apr 23, 2004 12:08 pm

we're working on an autoupdate system for future releases.

in the meantime manual updating of etpro_cheats.dat is what we have.

fwiw cheating-death uses static data and it's been reasonably successful.

Post by **bani** » Fri Apr 23, 2004 12:36 pm

Spark2 wrote:Yes, upgraded to rev 20 and still get reported as cheating (just got kicked again by friendly admins...).

can you connect up to the quaketheism server and see if you get kicked?

69.93.136.70:27969

it's running new code which should catch this linux/fedora false positive.

ReyalP · Post by **ReyalP** » Fri Apr 23, 2004 3:51 pm

It would nice if you at least kept sticky or something which listed all the known false postives, when they were fixed etc.

I would also suggest changing the ^1CHEATER and ^3CHEATER to something like ^1KNOWN CHEAT and ^3POSSIBLE CHEAT

Post by **bani** » Fri Apr 23, 2004 4:05 pm

SCDS_reyalP wrote:It would nice if you at least kept sticky or something which listed all the known false postives, when they were fixed etc.

i thought thats what this thead was for

read the first post, its pretty much that already...

Spark2 · Post by **Spark2** » Sat Apr 24, 2004 5:12 am

It doesn't kick me on that server, looks good...

I strongly agree that it should be worded differently when it's not a "sure cheat".

banimod / etpro / ettv forums

problems with anticheat

Linux Problems