
Originally Posted by
Foxxy Boxxy
It gives meaningful information wtf...... it gens a sig from a random part of the code and checks if that sig is contained in the new program.......
Vac does the same thing gens sigs random parts of the code and compare to data base so.... if you have ANY matching sigs there is no garentee your cheat is not detected.
I get what you mean when you say the % is meaningless unless its 100% or 0% and I agree but, 50% means it had one or more matching sigs. If Vac has already flaged one of those sigs then your new cheat is done. So technically the higher number of matching sigs found means high likelihood valve has found one or more of them too.
Except that sigbench only makes 1 signature per file, and compares those.
Which is completely different as to how VAC does it.
VAC is mostly focused on running code, code that is actually running in memory, while sigbench only compares binaries.
Simply add a new big feature to your hack (Like an aimbot class), and sigbench will go "Oh yea, completely different now m8"
Meanwhile VAC could just catch you again.
Even though both sigbench and VAC use signatures, the implementation is completely different.
That's why sigbench can't ever be used to determine if a hack is safe for VAC, and it might only give you a false sense of security.