Use same digest/signing algorithm as a release build

NEW
Assigned to

Status

()

Firefox for Android
Build Config & IDE Support
8 months ago
7 months ago

People

(Reporter: jlorenzo, Assigned: jlorenzo)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Assignee)

Description

8 months ago
Follow up of bug 1340093. There, attachment 8838078 [details] required devs to manually nuke ~/.android. :nalexander pointed out we could programmatically check the algos:

> keytool -list -keystore ~/.android/debug.keystore -storepass android -alias androiddebugkey -v

and remove them if they don't match SHA1withDSA. Let's try that and use the same algos as a release build.

Updated

7 months ago
Depends on: 1346968

Comment 1

7 months ago
We should allow for either SHA1withDSA or SHA1withRSA... the release key is the latter.
If we have to regenerate one of the keys to match, we should regenerate the nightly key and force all nightly and aurora users to reinstall, rather than the release key and force all beta+release users to reinstall.
You need to log in before you can comment on or make changes to this bug.