Closed jevonearth closed 5 years ago
There is an issue in yubihsm-wrap
with how Ed25519 keys are wrapped. I've pushed new code to the wrap_ed25519
branch. Are you able to build and test that?
Thank you for your patience @a-dma
I see that the yubihsm-wrap
branch was merged, so I tested with a guild from master at 7e458323323a1cb9601a69558cf236d48532a4eb
My import tests work now, so I think you can close this issue.
Will you be able to cut a new release of yubihsm2-sdk?
Glad to hear that your issue is solved.
We're planning a new release of the SDK relatively soon. No promise on a date just yet though.
Related to support
#78302
We are trying to build a tool that will allow users to export their key to pkcs8 format keys in order to import them into their Yubi HSM2 device.
For this tool we are targetting 3 algorithm ecp256, eck256 and ed25519. The two first are working wonderfully. Our users are able to export their key, wrap them using
yubihsm-wrap
and then import them into the HSM with no problemOur issue is with
ed25519
. We have tried several things in order to make it work, but we just realized that even if we generate a key withopenssl
we are not able to import it.Detailed steps are below, the final error message is;
If you could give me some directions regarding this is it would be very much appreciated. Thanks in advance
Nothing of note. We are using it with all defaults as far as we can tell.
We have posted the steps here: https://stackoverflow.com/questions/57185517/how-to-import-a-ed25519-private-key-into-yubi-hsm-2
and I will repeat a summary here again; I have also attached the shell script that I used to make this output, for your convenience. Note that in our lab, we are running the yubi connector daemon on host http://10.60.58.15:12345, and that is reflected in the below logs.
This is the debug output from the connector (running with the -d flag) from when we run the command "yubihsm-shell -C http://10.60.58.15:12345 -p password -a put-wrapped --wrap-id 30 --in private.yhw"