Am Sonntag, 22. April 2007 11:38 schrieb Nils Larsch:
does setting lock_login = true or cache_pins = true in the opensc
config help ?
cache_pins solves the problem. enable that by default?
if we change code/config before release anyway, what should
we do with the max_send_size issue / related
Hi All,
as you perhaps remember, I was not confident about the rewrite of the
PKCS#11 header files. So, I asked the RSA's opinion and I'm now glad to
share their reply with you:
My apologies for the lengthy delay in responding to your message.
This would appear to be within the spirit of
Andreas Jellinghaus wrote:
Am Sonntag, 22. April 2007 11:38 schrieb Nils Larsch:
does setting lock_login = true or cache_pins = true in the opensc
config help ?
cache_pins solves the problem. enable that by default?
if we change code/config before release anyway, what should
we do with the
Hi Allessandro,
(b) accrue appropriate acknowledgment to RSA.
too bad. they want fame, but ignore the side effect. berkeley
was changed their mind with the BSD license because of the ill
side effects. too bad RSA labs is not willing to do the same.
That said, I am not in a position to give
Hello,
I have a plan to write a PKCS#11 proxy which offers PKCS#11 interface
to application and work with PKCS#11 provider at daemon side.
This will enable to solve two issues:
1. Do not allow a PKCS#11 provider to mess with main process memory.
2. Allow single signon for user desktop, by
Hello,
I need driver for iKey 2032 on Windows XP 64-bit (AMD64). There is no plan to develop that driver from SafeNet (manufacturer, I was querying their support) nor XP 64 bit nor Vista 64 bit. Is there possible to use OpenSC source code to generate this driver? And, is OpenSC source code
