-
Notifications
You must be signed in to change notification settings - Fork 15
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
engine causes segmantation fault #2
Comments
in the engine, vault is for azure key vault. If you created a key in HSM, please use managedHsm as the prefix. I am adding the Managed HSM example soon. |
I noticed that in your error message, there is no
Maybe you are using the old code, could you pull the latest code and rebuild/retry? |
not reproduceable |
Thanks for new example. And in my environment some commands occured errors. (1)
In my windows 10 environment, I can use default openssl.cnf as not specified.
(2)
In my case it was nesessary to assign hsm local role to my account via this command:
(3) maybe p-256 is mistyped of P-256
|
(1) the sample openssl.cnf is provided in the repo |
Hello,
Thanks for great work.
I've tried to use this engine.
At first, I examined your nginx example.
I've do as followed the document sequence.
Then, it occured Segmentation Fault.
Is my procedure is wrong?
Thanks.
The text was updated successfully, but these errors were encountered: