We decided to implement the engine concept, but as far as I understood acts the
engine on a globally level, right?
But in our application we have two different TLS communication ways, is it
possible that our custom engine is only active for one transport way i.e. on
ssl context level?
Hi Tobias,
On 23/10/19 10:11, tobias.w...@t-systems.com wrote:
Our PKCS11 module development will discontinue and therefore I can`t use it
anymore, but the idea is great and very interesting.
To give more details we need a callback or similar mechanism to replace the
signature created in
> From: tobias.w...@t-systems.com [mailto:tobias.w...@t-systems.com]
> Sent: Wednesday, October 23, 2019 02:11
>
> Our PKCS11 module development will discontinue and therefore I can`t use it
> anymore, but the idea is great and very interesting.
> To give more details we need a callback or similar
lf, T-Systems
-Ursprüngliche Nachricht-
Von: openssl-users Im Auftrag von Michael
Wojcik
Gesendet: Dienstag, 22. Oktober 2019 17:00
An: openssl-users@openssl.org
Betreff: RE: openssl and external card reader support in TLS
> From: openssl-users [mailto:openssl-users-boun...@openssl.org] On
> Beha
> From: openssl-users [mailto:openssl-users-boun...@openssl.org] On Behalf Of
> tobias.w...@t-systems.com
> Sent: Tuesday, October 22, 2019 07:03
> I need to implement support for the external authentication of a card reader
> within a
> TLS handshake. We did this already with PKCS11 using the
I need to implement support for the external authentication of a card reader
within a TLS handshake. We did this already with PKCS11 using the C_Sign
function and it is working fine.
Now I need to implement the same functionality in another use case with openssl
for TLS handshake.
My Question
