The following comments are owned by whomever posted them. This site is not responsible for what they say.
Unpacking NTKrnl Protect 0.1
Authored by:
bpx on
Saturday, January 27 2007 @ 12:20 AM CET
hrrm, I agree, rdtsc trick is too well known to steal?
Anyway, protector will crash if you just continue after breaking on ret, because normaly the memory protect would cause an exception when it tries to execute. Olly thinks that we set a memory breakpoint when it is this protect. By changing ret to int3, it forces on the exception that gets removed by olly's mem-break handler.
Anyway, protector will crash if you just continue after breaking on ret, because normaly the memory protect would cause an exception when it tries to execute. Olly thinks that we set a memory breakpoint when it is this protect. By changing ret to int3, it forces on the exception that gets removed by olly's mem-break handler.