-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Add coverage for MSTG-CODE-9 on Android #2089
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not a real review yet, because I think the approach should maybe be a bit different. By focussing only on native files, the test would become a lot clearer.
…or MSTG-RESILIENCE-9 and add APKiD
Co-authored-by: Jeroen Beckers <info@dauntless.be>
Co-authored-by: Jeroen Beckers <info@dauntless.be>
Co-authored-by: Jeroen Beckers <info@dauntless.be>
Co-authored-by: Jeroen Beckers <info@dauntless.be>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Most of them are easy fixes :)
Document/0x05j-Testing-Resiliency-Against-Reverse-Engineering.md
Outdated
Show resolved
Hide resolved
Document/0x05j-Testing-Resiliency-Against-Reverse-Engineering.md
Outdated
Show resolved
Hide resolved
Co-authored-by: Jeroen Beckers <info@dauntless.be>
Co-authored-by: Jeroen Beckers <info@dauntless.be>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🥳
The Android test "Make Sure That Free Security Features Are Activated (MSTG-CODE-9)" was wrongly covering obfuscation. Now it's corrected and covers binary anti-exploitation protections.
Overview of all changes: