snipester
27th July 2006, 07:35
This was posted by Xantran at www.vacdisabled.com
VAC2 Information
Ok so you have all been banned? Correct? Ok, assuming most of you have, here is our information. Take it or leave it. Ok so there is a detection method that VAC/VAC2 uses called CRC detection. Google CRC for a complete definition on it but heres how it works mainly. Each file on a computer has a unique signature (CRC) and so each binary and loader has a unique CRC. So you inject a hack into CS therefore the CRC is loaded into memory (pretty sure). Hacks are detected by this by VAC2 seeing each CRC in memory and either if it sees the same CRC many times it marks it as a cheat OR the VAC team downloads each hack, gets a CRC from it, and adds it to the database to scan for. So when you join a server that CRC is checked against all the CRCs loaded into your memory/computer and if it finds one you sees you as cheating so therefore it bans you. Adding CRC's does not require updating the client VAC module and is handled purely on the VAC servers. This means that we ARE RIGHT when we say our logger says the last Client VAC Module Update was in December but we can not tell when the last time the servers were updated. This means that as far as we knew per our logger all cheats released after December were still VAC2 proof. We were wrong. We now understand that CRC detection which is easiest and most effective against public cheats was used to detect such hacks as the latest FSP, VDC: Catalyst, Ecstatic Cheat (before one released today), Mic Cheat, Pandasex, and so on and on the list goes on and on. To avoid CRC detection there are some things you can do...
As soon as a cheat is released use it for say 3 or 4 days and then put it down and never use it again.
Take a hex editor, change one string (the text in the binary), and that will then change the CRC of the binary (*.dll file) without corrupting anything.
Dont cheat at all.
Amongst other ways VAC detects things theres not much you can but rely on us. Our private hooking methods are VAC2 proof but we cant do anything about CRC detection except poly engine or polymorphism (changes the CRC everytime the hack loads) which none of us here have yet tried or really want to try to do.
As of last night I have informed the top cheat distributing sites to mark all cheats as detected until further notice. Hacks such as EC 12.14.6 are still VAC2 proof but FSP, VDC: Catalyst and others ARE NOT!!! Simple as that.
I think he is very right.
VAC2 Information
Ok so you have all been banned? Correct? Ok, assuming most of you have, here is our information. Take it or leave it. Ok so there is a detection method that VAC/VAC2 uses called CRC detection. Google CRC for a complete definition on it but heres how it works mainly. Each file on a computer has a unique signature (CRC) and so each binary and loader has a unique CRC. So you inject a hack into CS therefore the CRC is loaded into memory (pretty sure). Hacks are detected by this by VAC2 seeing each CRC in memory and either if it sees the same CRC many times it marks it as a cheat OR the VAC team downloads each hack, gets a CRC from it, and adds it to the database to scan for. So when you join a server that CRC is checked against all the CRCs loaded into your memory/computer and if it finds one you sees you as cheating so therefore it bans you. Adding CRC's does not require updating the client VAC module and is handled purely on the VAC servers. This means that we ARE RIGHT when we say our logger says the last Client VAC Module Update was in December but we can not tell when the last time the servers were updated. This means that as far as we knew per our logger all cheats released after December were still VAC2 proof. We were wrong. We now understand that CRC detection which is easiest and most effective against public cheats was used to detect such hacks as the latest FSP, VDC: Catalyst, Ecstatic Cheat (before one released today), Mic Cheat, Pandasex, and so on and on the list goes on and on. To avoid CRC detection there are some things you can do...
As soon as a cheat is released use it for say 3 or 4 days and then put it down and never use it again.
Take a hex editor, change one string (the text in the binary), and that will then change the CRC of the binary (*.dll file) without corrupting anything.
Dont cheat at all.
Amongst other ways VAC detects things theres not much you can but rely on us. Our private hooking methods are VAC2 proof but we cant do anything about CRC detection except poly engine or polymorphism (changes the CRC everytime the hack loads) which none of us here have yet tried or really want to try to do.
As of last night I have informed the top cheat distributing sites to mark all cheats as detected until further notice. Hacks such as EC 12.14.6 are still VAC2 proof but FSP, VDC: Catalyst and others ARE NOT!!! Simple as that.
I think he is very right.