Certificate REVOKED reason KEY_COMPROMISE
Blank517 opened this issue · comments
BootloadSpoofer v3.3
Android 14
LSPosed log
verbose_2023-12-18T11_47_01.906435.log
Key Attestation status
Speaking of keystore (as the screenshot shows the "keystore key" as culprit), the APK is signed using a debug certificate:
Number of signers: 1
Signer #1 certificate DN: C=US, O=Android, CN=Android Debug
Signer #1 certificate SHA-256 digest: 3e9c9e986f3a9e138b2e32b4806d8c744abcdc9999d221175a77bcc98a8c7f3f
Signer #1 certificate SHA-1 digest: 19ca5bb84398fe9d19ab06585350aaa73f9c23a0
Signer #1 certificate MD5 digest: 04678e33a5ac2432caf692b6cc555e80
Signer #1 key algorithm: RSA
Signer #1 key size (bits): 2048
Maybe a proper release key would help? And should that be unrelated, it would still be a good idea 😉
Yeah, one certificate is revoked. I won't use a working one, Google will ban it XD.
Just ignore the error.
And what about using a proper release key (for signing the APK) nevertheless? Or would that cause a "ban" by G?
Apologies if my question sounded stupid, but I'm no Android developer. I just see the warning that the app is signed using a debug key – I don't know if the two things are related. So can you please clarify? Would signing the APK with a proper release key cause the above issue, @chiteroman?
@chiteroman How are you able to get the private key used for signing the leaf certificate? Also, currently used key has been revoked by google because of which your module is not being able to bypass the check.
Are you going to update the keys in near future?