AFAIK, the public memory cheats can be detected very easily by VAC and most of them are detected. But of course, the privates ones, VAC rarely detect any of them, same for public ring 0 cheats, which are increasing those last years. I've seen many people getting banned for this. One of the most known memory cheat which work on many games and allow you to "freeze" any cvar value on HL1/HL2 is Cheat Engine, and you'll surely get banned for it (I used it to test things a few years ago on a HL1 account and got banned).
Then, maybe VALVe could add some sort of code for the detection of memory hacks to be automatic, like it would check for the server value, and if the client value is different or forced to an other value, you would get kicked from the server? (not VAC banned since people could probably use some sort of plugin to trigger the detection) The main problem in L4D is the VPKs files not being checked for modifications by Steam, like it does for GCF. Of course modders would then cry because they can't modify the VPKs, and ATM that's what they're doing to use custom skins. This could be fixed by allowing files to be loaded outside of the VPKs. Then, we could just use sv_pure 2 and it would load content from the VPK, exactly like it does on other source games for GCF (or use the from_steam parameter with sv_pure 1). And of course, disallow $ignoreZ to be used on any player models at least. I don't understand why this hasn't been done yet. 2009/5/7 w4rezz <[email protected]> > sv_pure can be bypassed easily... there are lots of "sv_pure bypass" > what use game memory editing method, > sv_pure bypass works only if server has sv_pure 1, if its 1, it can be > bypassed by memory hack on client, and memory cheats arent detected by > VAC, becouse VAC just dont check for those memory changes, what we can > see on PunkBuster... so if will be sv_pure fixed in L4D, can be still > bypassed easy like in css/tf2 with simple program running on > background. > > So, main problems are: > 1. VAC dont check for memory cheats > 2. sv_pure can be disabled on client by memory editing or other > exploits ( alt+tab ) > 3. sv_pure > 4. IgnoreZ is allowed on all textures in TF2/L4D > > Becouse of thoose problems we can actualy: > - Play with wallhack on more then 90% of TF2 servers > - Play with wallhack on all L4D servers > - Play with any type of material hack in css/tf2/l4d if we use memory > sv_pure bypass > > > 2009/5/7 AnAkIn . <[email protected]>: > > My previous message wasn't posted, so I'll try to send it again: > > > > "Isn't the pure_server_whitelist.txt already existing in the hl2/ folder > and > > automatically loaded? > > I guess I always had it here and never in my tf/ folder, but then I might > > have put it here, not sure. > > > > But then, the default pure_server_whitelist.txt still allow custom > models, > > and as you said, many admins got no idea of what that file is, and leave > it > > as default. > > > > If they fix sv_pure 1 in L4D, so we can do CRC32 checks on them, there is > an > > other problem : CRC32 checks can be bypassed. I've heard there are some > > programs which allow you to change the CRC32, so you could make it match > the > > one of real file. :/" > > > > > > > >> 2009/5/6 w4rezz <[email protected]> > >> > >>> There is no whitelist in TF2 , there is file called whitelist.cfg what > >>> is pretty ignored by game, you have to create > >>> pure_server_whitelist.txt, and type rules here, but do you think every > >>> admin know it ? They just start server by using hldsupdatetool (any > >>> tutorial on internet ) and install Sourcemod + plugins , thats all > >>> what normal admin can do, why you think every admin know how block > >>> wallhacked textures? That pretty worked in cs source, blocking ignoreZ > >>> function on sv_consistency 1 servers mean > >>> skins still works, its not crc32 check but it block wallhack, and if > >>> you wanna crc32 check (skins not allowed) you will use sv_pure, why > >>> isnt this method used in TF2 and L4D too ? > >>> > >>> Its looks pretty stupid if cheat developers give main credits to Valve > >>> for enabling ignoreZ.. > >>> > >>> > >> > > _______________________________________________ > > To unsubscribe, edit your list preferences, or view the list archives, > please visit: > > http://list.valvesoftware.com/mailman/listinfo/hlds_linux > > > > _______________________________________________ > To unsubscribe, edit your list preferences, or view the list archives, > please visit: > http://list.valvesoftware.com/mailman/listinfo/hlds_linux > _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
