-
Notifications
You must be signed in to change notification settings - Fork 34
Description
I get an error "package is invalid: crx_signature_verification_initialization_failed" when trying to install a packaged app that has been generated using crxmake 2.2.0.
That must come from crxmake since manually packaging in Chrome (latest stable 31.0.1650.63, windows 8) with the same pem file does not raise the error.
The crx format must have changed, because the header looks like 4372 3234 0200 0000 3C01 0000 0001 0000 (hex), which according to the current doc (http://developer.chrome.com/extensions/crx.html) means a public key length of 15361 bytes, and a signature length of 1 byte, which does not make any sense.
I've also noticed that the pem file generated by chrome is now 1703 bytes long, when it used to be 916 bytes long. Could it be that crxmake does not handle the new pem file format?