Commit Graph

5 Commits

Author SHA1 Message Date
Alex Klyubin
702ed27285 Switch from SHA-1 to SHA-256 for new signing key certs.
This is to move OTA update package verification logic for new Android
devices from SHA-1 to SHA-256.

Prior to this change the script which generates new signing keys
used SHA-1 in certificates. This change switches the script from SHA-1
to SHA-256. The reason is that OTA updates are accepted only if they
are signed using the same digest algorithm as in the certificate.

Bug: 25643280
Bug: 20580998
Change-Id: I9babe85946a43697aeb4309837504aea25e26763
2016-02-17 13:19:41 -08:00
Kenny Root
7f3f83e0e3 make_key: reduce raciness of password input
Bug: 14595245
Change-Id: I8a9e4f2c46aa3c85763975c5cb7a47df197f7746
2014-07-31 13:00:12 -07:00
Kenny Root
98356f64a8 make_key: add EC key generation support
Add the ability to create EC keys for use in creating ECDSA signatures.

Change-Id: Ia1654b69056413d66275ea6c55d8273f5f09f5c6
2013-11-06 09:25:28 -08:00
Baligh Uddin
6b03c84e6e Use more secure exponent for generating keys
Bug: 7246090
Change-Id: Ic6cbac975fcb96b436e27a87b1f81b5e3dac6321
2012-09-28 11:30:10 -07:00
Doug Zongker
4c95917590 add one script to make release keys
This script can replace the copies of mkkey.sh sprinkled all over the
tree.  It prompts nicely for passwords, avoids writing the raw private
key to disk, and always generates certs that use sha1WithRSAEncryption.
2009-12-01 12:32:00 -08:00