We Need TO kill VAC!!

[SolidSnake]

damn vac is all over us, we need to make something, even though im no coder, but sureley somone can make a tool so it disables vac? anyone?:ermm:

[greenball]

there are already tools but if you make them public the
bugs they expolit will be fixed so there is no sense in releasing
a public VAC-killer

[tinymonkey]

could you possibly PM me a hint to these tools, your inbox is full.

I understand if you dont want to tell anybody.

Thanks,
tiny :D

[greenball]

if i didnt want to tell anybody, why should i tell you?

[tinymonkey]

you misunderstood what i said, i said IF because I dont know if you will give it to anybody, so would you?

[greenball]

i dont have it ... but i know some silvers ...

[tinymonkey]

oh:(

[o({})o]

There is no tool to dissable VAC....Unless you are server admin of course.....

[tinymonkey]

yea i thought that "tools" to kill VAC sounded a little strange

[Cyanide.dk]

I think it's possbile to "disable" VAC, without being a Server admin.
Can't remember where I read this, but when you do a memory dump on VAC, you can actually see which dll files that are loaded into memory. Then load the dll file into a decompiler and hack the dll, somehow. of course the dll is encrypted, so you would also need some kind of decrypting software.
But I don't think, that it's impossbile, to do such things. Might take a hell of a lot time, and I'm not sure, that it's even worth the try.
Anyway, I'm not a coder, so I'm not very much into this kind of stuff :-/

[tinymonkey]

yea pharlap made a thread about it in the OGC forums...Dumping VAC (im not sure but i think that is what you mean)

[CHEETAH0E]

look, cs doesn't read the dll in the cl_dll's folder, it is encrypted, then at run-time, decrypted and in the memory banks of your computer, you can verify this, by opening counter-strike, minimizing it and renaming the client.dll

all you have to do is make a memory scanner, and get the code out of memory, it's not that difficult, especially since you can load a dll into memory completely, then hook it from there.

Vac cannot scan your systems memory without a warning saying "We will scan your hardrives memory", otherwise it is illegal, and they can have legal action against them for invasion of privacy. Simply put, code the dll into memory where hl.exe codes it, meaning you take the space before it does, and you have your dll loaded rather than the real one :)

[Dark_Omen]

Originally posted by CHEETAH
look, cs doesn't read the dll in the cl_dll's folder, it is encrypted, then at run-time, decrypted and in the memory banks of your computer, you can verify this, by opening counter-strike, minimizing it and renaming the client.dll

all you have to do is make a memory scanner, and get the code out of memory, it's not that difficult, especially since you can load a dll into memory completely, then hook it from there.

Vac cannot scan your systems memory without a warning saying "We will scan your hardrives memory", otherwise it is illegal, and they can have legal action against them for invasion of privacy. Simply put, code the dll into memory where hl.exe codes it, meaning you take the space before it does, and you have your dll loaded rather than the real one :)

Speaking of that the tool that would be most likely be possible to grab the stuff out would be procdump32. Though there are some risk of access violations to the address. Could always try.

[DarkCoder]

Very intresting