You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Input from Christian Damour, security expert, FIME
I would recommend using whitebox cryptography and a unique storage key per device.
Potential security mechanisms to implement include:
• Anti-Tampering
• Anti-Rooting
• Anti-Instrumentation
• Anti-Emulation
• Anti-Debugging
• Device-Binding
• Obfuscation
• White-box Cryptography
Many of these are available from specialist software technology providers. They allow
developers to adopt solutions which have already passed the complex security evaluation.
For instance for obfuscation, Proguard (freeware) is not sufficient and Dexguard offers appropriate level security (commercial solution).
"For obfuscating any string resources or an asset file, use a library like StringCare."
I have never heard about StringCare in the context of payment. I think it is Open Source and provides weak obfuscation feature.
The text was updated successfully, but these errors were encountered:
Input from Christian Damour, security expert, FIME
I would recommend using whitebox cryptography and a unique storage key per device.
Potential security mechanisms to implement include:
• Anti-Tampering
• Anti-Rooting
• Anti-Instrumentation
• Anti-Emulation
• Anti-Debugging
• Device-Binding
• Obfuscation
• White-box Cryptography
Many of these are available from specialist software technology providers. They allow
developers to adopt solutions which have already passed the complex security evaluation.
For instance for obfuscation, Proguard (freeware) is not sufficient and Dexguard offers appropriate level security (commercial solution).
"For obfuscating any string resources or an asset file, use a library like StringCare."
I have never heard about StringCare in the context of payment. I think it is Open Source and provides weak obfuscation feature.
The text was updated successfully, but these errors were encountered: