-
Notifications
You must be signed in to change notification settings - Fork 94
Signing key changed? #211
Copy link
Copy link
Open
Description
What happened to your signing key? The latest release comes with a different one, and hence was rejected (no updates possible anyway, as Android would reject this as well).
Signature before:
Signer #1 certificate DN: CN=Sapate Vaibhav, OU=sappu, O=VaibhavCodeClub, L=pune, ST=MH, C=IN
Signer #1 certificate SHA-256 digest: 5c1100494e222e297ba4e2e6b90707a94bc1c9322dce6de38f25f311d3f93dd0
Signer #1 certificate SHA-1 digest: 742efe0ab7cbdff829da1faab50c23e8a46c26fe
Signer #1 certificate MD5 digest: e669870c03b2f9f24213c3fc67afbd53
Signature now:
Signer #1 certificate DN: CN=Vaibhav Sapate, OU=VaibhavCodeClub, O=VaibhavCodeClub, L=Pune, ST=MH, C=IN
Signer #1 certificate SHA-256 digest: 8a21b93b031caff2b70100cbc8ccbba0fdbbbb214963a74159d57c4007942669
Signer #1 certificate SHA-1 digest: e9a752148a8c446fd5b8887fd8c78f586025c6e8
Signer #1 certificate MD5 digest: 46b18b93401e7d35fe0d382eec839b8d
Updates will be disabled at IzzyOnDroid until this is solved. For background please see: How to keep your key safe and what measures to take for the event of loss?
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels