Skip to content
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

onTamperDetected is executed when running on physical device #12

Closed
neroaCu opened this issue Feb 26, 2022 · 1 comment
Closed

onTamperDetected is executed when running on physical device #12

neroaCu opened this issue Feb 26, 2022 · 1 comment

Comments

@neroaCu
Copy link

neroaCu commented Feb 26, 2022

Hi,

Can you tell me under what conditions this plugin would detect it as a tampering case?

I enabled this onTamperDetected feature in android and found that it was invoked on a physical device (developer mode is enable) and simulator as well. Is this expected behaviour? for example, it restricts the app must be download from google/Apple Store?

Or does it means I did something else wrong? like the expectedSigningCertificateHash is wrong?

Please help. Thanks

@talsec-app
Copy link
Member

Hello,

application is considered tampered if it has incorrect package name or if it was signed/resigned with an unknown signing key (signing certificate mismatch). If the application is installed from an untrusted application store, onUntrustedInstallationDetected is triggered. Please verify, that your expectedSigningCertificateHash is correct. You can use this link for Base64 -> Hex conversion: https://base64.guru/converter/decode/hex
We will try to add expectedSigningCertificateHash checks to the next version of Talsec.

Talsec Team

@talsec-app talsec-app pinned this issue Mar 8, 2022
@rakesh0689 rakesh0689 mentioned this issue Mar 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants