Götz Babin-Ebell wrote:
In my view it lacks the following features:
1. Allow the user to specify his own PKCS#11 library.
2. Generate a new key.
This is wide outside of the OpenVPN usage.
Is is to be implemented in an PKCS#11 (key) managemement tool
but NOT in an VPN daemon.
The update is for
Hi,
> >> I've made easy-rsa 2.0 support for PKCS#11 (it makes a certificate from a
> >> token). If you are interested, then it is at
> >>
> > In my view it lacks the following features:
> > 1. Allow the user to specify his own PKCS#11 library.
> > 2. Generate a new key.
>
> This is wide outside
> Ondra Medek wrote:
>> Hi,
>>
>> I've made easy-rsa 2.0 support for PKCS#11 (it makes a certificate from a
>> token). If you are interested, then it is at
>>
>
> Hello,
>
> Thank you for your patch.
>
> In my view it lacks the following features:
> 1. Allow the user to specify his own PKCS#11
Hi,
> In my view it lacks the following features:
> 1. Allow the user to specify his own PKCS#11 library.
> 2. Generate a new key.
> 3. Load the X.509 certificate into the token.
>
> Now when I think of it, issue#1 can be solved by a symbolic
> link, you can have the configuration point to a lo
Ondra Medek wrote:
Hi,
I've made easy-rsa 2.0 support for PKCS#11 (it makes a certificate from a
token). If you are interested, then it is at
Hello,
Thank you for your patch.
In my view it lacks the following features:
1. Allow the user to specify his own PKCS#11 library.
2. Generate a new
