Re: [Openvpn-devel] [PATCH v3] Allow PKCS#11 uri to be used as --cert and --key file names

2022-01-27 Thread Gert Doering
Hi, On Tue, Jan 25, 2022 at 12:02:44PM -0500, Selva Nair wrote: > > In its simplest form, just have > > > > --cert 'pkcs11:id=%01' > > I'm withdrawing this patch as it has no prospects going forward with > engines on their way out in > OpenSSL 3.0 and beyond. Withdrawing is also an honourable

Re: [Openvpn-devel] [PATCH v3] Allow PKCS#11 uri to be used as --cert and --key file names

2022-01-25 Thread Selva Nair
On Sun, Aug 15, 2021 at 6:26 PM wrote: > From: Selva Nair > > v2 changes > - do not allow so-path embedded in cert and key uri > - add --pkcs11-engine option to optionally specify the > engine and provider module to use > v3: rebase to master > > If either --cert or --key is

[Openvpn-devel] [PATCH v3] Allow PKCS#11 uri to be used as --cert and --key file names

2021-08-15 Thread selva . nair
From: Selva Nair v2 changes - do not allow so-path embedded in cert and key uri - add --pkcs11-engine option to optionally specify the engine and provider module to use v3: rebase to master If either --cert or --key is specified as a PKCS#11 uri, try to load the certificate and key