-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
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
Protection-Tests #16
Comments
What maybe work (ig?) is to write a little program which obfuscate an example mod for a game and then move it to the game mods folder and check if any exceptions related to BitMono have been thrown (by taking the stdout or checking the game log files) |
Could be a good one |
I asked a question on stackoverflow, I already got an interesting question, but still, I'm waiting for something else and then I will start working on it |
The best way I realized:
The only thing is that possible to check if there are no BadImageException or other weird exceptions and initialize only from Module cctor and Main |
Get the runtime mono version (useful in future tests): System.Runtime.InteropServices.RuntimeInformation.FrameworkDescription OR Type type = Type.GetType("Mono.Runtime");
if (type != null)
{
MethodInfo displayName = type.GetMethod("GetDisplayName", BindingFlags.NonPublic | BindingFlags.Static);
if (displayName != null)
Debug.Log(displayName.Invoke(null, null));
} |
Use PEVerify |
Maybe in future will be made, but now I don't see a reason for that, too much complex and it anyway won't test it as a real person would test, closing it |
Seems as Unit-Tests or something like that but for protections
The problem:
How to understand that protection is working fine and it works under Mono without issues, how to automate this?
Current ways:
The text was updated successfully, but these errors were encountered: