Thank you!
dnSpy already takes care of .NET specific debugging detection!
regarding method of standalone process protection,
say I use this approach for .net app:
2.0.1 Standalone (debugger-independent)
InjectorCLI.exe ”process name” ”HookLibrary.dll path”
For example: InjectorCLI.exe crackme.exe C:\HookLibrary.dll
will I be able after this run to debug the app using dnSpy and the app will be blind to native dbg detectors?
|