| Could It Work? [message #49356] |
Sat, 27 September 2003 05:37   |
destruktv
Messages: 14
Registered: September 2003
Karma:
|
Recruit |
|
|
A very basic appriach, any script kiddie would try that first  . I'd be surprised if the Renguard team had not covered that. The best way to check what the directory of the (executing) Renegade process is, is ofcourse in its runtime state.
CreateProcess(LPCWSTR lpszImageName, LPCWSTR lpszCmdLine,
LPSECURITY_ATTRIBUTES lpsaProcess, LPSECURITY_ATTRIBUTES lpsaThread, BOOL fInheritHandles, DWORD fdwCreate, LPVOID lpvEnvironment, LPWSTR lpszCurDir, LPSTARTUPINFOW lpsiStartInfo,
LPPROCESS_INFORMATION lppiProcInfo);
The above API function's first parameter by default when windows creates a process specifies the full path and filename of the module (executable) to execute.
This parameter can easily be checked to determine (running) Renegade's directory.
Ofcourse there are other issues that need to be considered even after that, but to bypass this, we already require some skills that most "lame kids who cheat" don't have.
Cheers,
D.
|
|
|
|
Search
Help
Members
Register
Login
Home
