To update this thread. Please follow the commentary on the
https://github.com/OpenSC/libp11/issues/249
From: "Blumenthal, Uri - 0553 - MITLL"
Date: Friday, September 21, 2018 at 5:07 AM
To: "Paras Shah (parashah)" , "openssl-users@openssl.org"
Cc: Nicola
Subjec
.
When I recompiled with openssl-1.0.2p, it worked fine. See
https://github.com/OpenSC/libp11/issues/249 for details.
From: "Paras Shah (parashah)"
Date: Tuesday, September 18, 2018 at 10:06 AM
To: Nicola , "openssl-users@openssl.org"
Subject: Re: [openssl-users] Softhsm + eng
Sure. I will open the issue.
From: Nicola
Date: Monday, September 17, 2018 at 10:05 PM
To: "Paras Shah (parashah)" , "openssl-users@openssl.org"
Subject: Re: [openssl-users] Softhsm + engine_pkcs11 + openssl with EC keys
fail.
Would it be possible for you to open this a
I had the same doubt. I have x-posed this question on the opensc mailing list
as well.
On 9/17/18, 3:37 PM, "openssl-users on behalf of Matt Caswell"
wrote:
Perhaps the pkcs11 engine does not support ed25519 keys?
Matt
On 17/09/18 22:05, Paras Shah (par
In message <4ac69fc3-bec7-46f6-882a-671196fc0...@contoso.com> on Mon, 17
Sep 2018 20:59:59 +, "Paras Shah (parashah)" said:
> 4. Import the key into softhsm
>
> []:~$ softhsm2-util --import ~/tmp/secp256k1-key.pem.pkcs8 --label "ec
key" -
I get the following error when I try to access the ed25519 key stored in
SoftHSM via the openssl engine interface using engine_pkcs11.
[]:~$ openssl pkey -in
"pkcs11:model=SoftHSM%20v2;manufacturer=SoftHSM%20project;serial=6a160d52b750862f;token=token%202.5.0-rc1;id=%22%22;object=ed25519%20leaf%
I have softhsm-v2.5.0-rc1 which has ec keys imported in it. Now, when I try to
use these keys from openssl CLI using the pkcs11 engine, it fails.
1. SoftHSM version
[]:~$ softhsm2-util --version
2.5.0rc1
2. SoftHSM token init
[]:~$ softhsm2-util --init-token --slot 0 --label "token 2.5.0-rc1"
According to RFC 2246, the alert number 80 represents an "internal error".
Here is the description from the RFC
internal_error
An internal error unrelated to the peer or the correctness of the
protocol makes it impossible to continue (such as a memory
allocation failure). T
