-
Notifications
You must be signed in to change notification settings - Fork 70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
API for public PKCS PEM string #84
Comments
So if I understand well, you are asking to generate a privateKey with Does the command |
Not exactly. For each extension there is a manifest.json with "key" property. |
Hm I see. There is a method to generate a public key: https://github.com/oncletom/crx/blob/120c3611f07e907159580974f85dfcb1b4b8b0dc/src/crx.js#L142-L154
Would that work? |
It is not the same. |
I see, that's something I never looked out (their difference of use of the various formats). As far as I can see, it's just a matter of passing a different parameter to the There is maybe a way to derive a PEM key from a DER key but it looks fine to change the signature of the What do you think? The |
Yeah, possible solution with default to der. |
I think not bad. I use this code.
|
I had to do it manually instead of using crx object.
This key in PKCS format without line ending and header, footer is used in 'key' property in the manifest.
https://developer.chrome.com/apps/manifest/key
This allows to have consistent extension id for unpacked extension placed in any folder.
The text was updated successfully, but these errors were encountered: