We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I'd expect the DebugPort to have a valid pointer if the status was successful? Which also then indicates the debugger port is active?
Anti-DebugNET/Anti-DebugNET/AntiDebug/DebugProtect2.cs
Line 73 in fce1a11
The text was updated successfully, but these errors were encountered:
Yes, that's correct; sorry about that.
I might have done small mistakes due to being rushed to write it... please use it with a grain of salt and always test.
Soon, I will update the code with improved checks, more checks and system calls.
Sorry, something went wrong.
private static int CheckDebugPort() { NtStatus status; IntPtr DebugPort = IntPtr.Zero; int ReturnLength; unsafe { status = NtQueryInformationProcess(System.Diagnostics.Process.GetCurrentProcess().Handle, PROCESSINFOCLASS.ProcessDebugPort, out DebugPort, Marshal.SizeOf(DebugPort), out ReturnLength); if (status == NtStatus.Success && DebugPort != IntPtr.Zero) { return 1; } } return 0; }
No branches or pull requests
I'd expect the DebugPort to have a valid pointer if the status was successful?
Which also then indicates the debugger port is active?
Anti-DebugNET/Anti-DebugNET/AntiDebug/DebugProtect2.cs
Line 73 in fce1a11
The text was updated successfully, but these errors were encountered: