Wallhack Protection Idea

[Arm0r]

O.k. im no coder or anything, but I was wondering if this idea is in anyway doable.   O.k. now people have a.c and such and the server has wall protection but I was thinking...is there anyway to have the server randomly make the users client take a screenshot and autosend it to a databank admins can look upon?  I thought it was a pretty cool idea, and if it work would be red handed, un-denyable evidence of said hack.  just a thought, anyone have any imput id be glad to see.

[console]

Hi,

It's a nice idea, but it is undermined by the same fundamental flaw that makes everything so challenging in this area.

The client can simply lie.

There is no way for the server to 'make' the client do anything.  The server can merely ask.

If the client sees, oh, they're asking for a screenshot... The person writing a hacked client will just say, ok, turn off the hax for one frame, capture the screen image, and turn the hax back on.  Then send the "clean" screenshot back to the server.


Regards,

[Whirlingdervish]

there is a way to stuff a screenshot command to a users client..
sending it to a remote destination might be a bit more tricky.

I have seen one example where an admin stuffed a number of screenshot commands and then compiled the resulting pics into an animated gif that proved to be an effective POV demo..


the biggest problem would be storing the large number of images and having someone willing to visually inspect them for clues that would show wallhacking.


it would also prove redundant, due to a little known feature of the TS servers that incapacitates most known wallhacks.
I'll leave it up to the admins/owner to describe that system as I don't know exactly how it works.

(I have a suspicion that the server checks what you can currently see and only sends you packets that have that information instead of a packet that contains the location of every entity on the map at any given second.)


 

[Arm0r]

Im probably dead wrong, but I figure Quake 2 is such an aged game, people creating hacks are minimal at best.  Efforts from people like R1CH are what keep the game pure these days , but I just thought of this as a possibly tricky way of detection.   Surley an anticheat hack could get around it eventually, but I believe lag and such may make a hack for it hard to come by.   Id love to see R1CH's imput on this him being the man when it comes to this stuff, though I know he's usually very busy    Dunno if it's because I don't like losing (who does?) but sometimes I suspect people but hardly act on it, I might say "nice walls" all in fun to stir people up, but it's a cheap laugh.  But when some get so up in arms about it and so defensive it makes me wonder (but then again id get defensive to if someone was calling me a hack) so I guess it's a double edged sword and you just hope for the best.

[jägermonsta]

hmm... How bout putting up a server that hosts the Quake2 client for users to run remotely. Locking out the ability for players to change any Quake2 files but a user config.

[console]

[quote author=j

[reaper]

you can always spectate someone with two pc's, and just have the monitor next to you, don't know how much effort people should be putting into this anti-cheat stuff, just play with people you trust.  I am curious if you can hack R1CH's anti-cheat, without hacking the server itself, or if you can authenticate the client to the server, i'm not to sure how his system works.

[console]

you can always spectate someone with two pc's, and just have the monitor next to you, don't know how much effort people should be putting into this anti-cheat stuff, just play with people you trust.

Note that if an admin is around, we tend to look closely when someone is connected more than once from a given IP.  Especially if one of the clients is in spectator mode.

I am curious if you can hack R1CH's anti-cheat, without hacking the server itself, or if you can authenticate the client to the server, i'm not to sure how his system works.

Just start with the fundamentals and work backward. 

Any client can be hacked, the trick is to make it difficult to hack, and keep it a moving target, so as to have the optimal chance of staying ahead of the hackers, and rendering old hacks useless when they are discovered.


Regards,

[[BTF]Defiant!]

[quote author=j

[console]

in some years network speeds will allow near real-time, high-resolution video.  Of course, this doesn't "solve" the problem because one could still run a memory-resident program which auto-aims based upon viewing the rendered video frames.  (CounterStrike was hit with such an aimbot.)

Hahaha, no way, how funny. 

I was imagining the possibility of such an aimbot as I was talking about streaming video in the earlier post--however I would never have guessed someone had actually done it!

:lollerskates:

[[BTF]Defiant!]

in some years network speeds will allow near real-time, high-resolution video.  Of course, this doesn't "solve" the problem because one could still run a memory-resident program which auto-aims based upon viewing the rendered video frames.  (CounterStrike was hit with such an aimbot.)

Hahaha, no way, how funny. 

I was imagining the possibility of such an aimbot as I was talking about streaming video in the earlier post--however I would never have guessed someone had actually done it!

:lollerskates:

Well the story may be fictitious; but, it goes like this...

Clan A was suspected of cheating.  The admins from Clan B tried to figure out how they were cheating.  As the story goes, one of the Clan B players had a wall spray which matched their teamskin color.  During a match, Clan A players' shots would snap and hit the wall spray even though it was obviously not a player.  Busted!

What makes me think this is fictitious is that dead players would keep the same teamskin color, so unless those get a different color or disappear I don't see how it would work.

In any case, it was another argument for running an external monitoring program like PunkBuster to check for memory resident programs / hacks.

Def