Posted: Sun Nov 23, 2008 10:02 pm
The AAC settings may be more effective this time.
Restricted Mode no longer obtains the path to the process nor its name because the Windows® functions that do that internally call ReadProcessMemory() on the target process, which was what was being detected before.
Because of this simple call, previous AAC settings would have no effect, since Windows® would be calling ReadProcessMemory() directly instead of using the MHS kernel functions.
There is still one possible loophole left, but patching it will take away a lot of MHS’s functionality. But it may be worth it if it works, since it isn’t called “Restricted Mode” for nothing…
But before that, it is best to see if AAC settings will work better together with the new Restricted Mode.
L. Spiro
Restricted Mode no longer obtains the path to the process nor its name because the Windows® functions that do that internally call ReadProcessMemory() on the target process, which was what was being detected before.
Because of this simple call, previous AAC settings would have no effect, since Windows® would be calling ReadProcessMemory() directly instead of using the MHS kernel functions.
There is still one possible loophole left, but patching it will take away a lot of MHS’s functionality. But it may be worth it if it works, since it isn’t called “Restricted Mode” for nothing…
But before that, it is best to see if AAC settings will work better together with the new Restricted Mode.
L. Spiro