g out everywhere
On Mon, Jun 03, 2019 at 02:52:42PM -0700, Erik Madsen wrote:
> if (typeof options.clientCertEngine === 'string') {
> if (c.context.setClientCertEngine)
> c.context.setClientCertEngine(options.clientCertEngine);
>
> options.clientCertEngine is just th
and it is calling openssl function:
SSL_CTX_set_client_cert_engine (SSL_CTX *ctx, ENGINE *e)
am I wrong that there should be a second argument passed from Node to
Openssl?
Really appreciate all your support
On 6/3/19 12:58 PM, Viktor Dukhovni wrote:
On Mon, Jun 03, 2019 at 12:54:46PM -0700, E
any thoughts here?
On 6/3/19 10:03 AM, Erik Madsen wrote:
Is there any possibility of setting second argument here from config?
SSL_CTX_set_client_cert_engine (SSL_CTX * ctx, ENGINE * )
I think at this point it's a Node issue not allowing for an engine to
be used for the key...I know
ect: Re: osf-contact Striking out everywhere
On Mon, Jun 03, 2019 at 04:41:47PM +0100, Matt Caswell wrote:
> On 03/06/2019 15:16, Erik Madsen wrote:
>
> > Thanks for the reply! Is there any link for avail variables for
> > openssl.conf?
>
> See:
>
> http
02 19:14:29 PDT 2019
To: "openssl-users@openssl.org"
Subject: Re: -keyform ENG and NodeJS
> On Jun 2, 2019, at 9:47 PM, Erik Madsen wrote:
>
> It is TLS and we want Root Of Trust from a non exportable, non readable
> Private key on the Hardware Security Module.
>
enssl-users@openssl.org
Subject: Re: -keyform ENG and NodeJS
On Sun, Jun 02, 2019 at 05:49:10PM -0700, Erik Madsen wrote:
> I am using a Hardware Security Module. Both s_client and cURL work fine
> due to we can use the CLI "-keyform ENG" for s_client and "--key-type
&g
I am using a Hardware Security Module. Both s_client and cURL work fine
due to we can use the CLI "-keyform ENG" for s_client and "--key-type
ENG" for curl
Is it possible to specify this in the openssl.cnf file instead of the CLI?
For testing this, the following works:
openssl s_client -conn
