Not only that, but it sounds like there's a way for servers to force clients to execute commands not marked FCVAR_SERVER_CAN_EXECUTE, which would be a security hole.

On 9/10/2012 9:47 AM, Drogen Viech wrote:
What the hell? Servers can tell the client to take screenshots *and*
tell them to upload them to the server? Whatever happened about
privacy?

2012/9/8 lwf <[email protected]>:
http://etf2l.org/forum/general/topic-21038/page-24/?recent=406717#post-406387

This is absolutely brilliant, great job! Now just imagine having
something like Greenlight to go through those...

I'm not even going to bother asking you to open source it but please,
at least consider releasing a "stable" version with that doesn't open
connection (no auto-update or reports to you or anywhere else, no
offense) and has no undocumented features (now or later). I'd really
like to use this, we should have had this long ago.

On Wed, Apr 11, 2012 at 7:23 PM, AnAkIn . <[email protected]> wrote:
Hi,

As Valve is too lazy to do anything about hacks, I started working
back in January on a plugin that can detect:
- POTENTIAL triggerbotters
- Prediction hacks (crit hacks/no spread hacks)
- An anti-speedhack bypass exploit

Triggerbots:
To make it clear as some people I gave it to didn’t understand, the
detection is kind of “heuristic” (I won’t explain in detail, if I do
then the cheat coders will bypass it in no time), so it’s not because
someone got detected that he is surely cheating. It’s just a tool to
help you find people that can potentially cheat and you can just check
the STV demos then to confirm that they cheat or not.

The most detections for a single person in the less timespan you will
find in the log, the more likely he is using a triggerbot.

Prediction hacks:
I guess this is what will interest most people on this list, it
detects the crit hacks that does 100% crits all the time which is an
engine exploit which has been added into many hacks lately. It's also
used for various no spread/low spread hacks.

The detections get printed to a log called TriggerBotDetections.log in
tf/ (and are also sent to me) on EVERY MAP change or when all players
have disconnected from the server. It’s important to note this
otherwise you could loose all the detections (especially if your
server automatically restarts every night). There is a simple reason
for this: writing in a file while you play can cause lags, especially
if someone is getting detected a lot.

Download: http://tftrue.redline-utilities.net/TriggerBotDetector.zip

--
Best regards,
AnAkIn

_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux


_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux

Reply via email to