Do not merge: example for cert generation and extension build #18
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…tificate and building the CEP extension from that.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Don't merge this. It's just an example.
The gist: I've had to disable the timestamping of the signing process, and then see the gotchas below.
Gotchas: The certificate password needs to be at least 6-characters long. The
ZXPSignCmdutility doesn't specify that, and if you give it fewer it'll just fail with a cryptic message. Note the other fields filled out in theenv.mkrelated to the certificate, as well, and do something similar. It's not super critical what the specific values are, but it appears to be important that they're filled in.Once your
env.mkis setup similar to what I have here (but with a real password, please...and don't commit theenv.mkonce you've modified it locally), you'll be able to run the make command to generate a p12 file.Once you have your p12 generated on disk, you can run the make sign command to build the extension and sign it using your certificate.