Peter Gubis wrote:
On 13. 3. 2010 0:37, John R Pierce wrote:
our security auditors yanked the token out, and the client continues
to work, ..
you'll probably need to listen for token removal event and destroy this
ssl session after that.
It is working for us in this way. Session should be r
On 13. 3. 2010 0:37, John R Pierce wrote:
> we have a client-server application pair (ok, the server side is
> tomcat), the client is using an Aladdin eToken w/ openssl and
> engine_pkcs11 and aladdin's driver. thats all fine and working now.
> the client application has long running persistenc
