2007/4/9, Robert Relyea <[EMAIL PROTECTED]>:
Preallocation of slots is a standard technique to support hotplugging.
Before PKCS #11 2.20, PKCS #11 modules were not allowed to change their
slot count between C_Initialize and C_Finalize. Even after PKCS #11
2.20, applications don't always query the
Martin Paljak wrote:
On 09.04.2007, at 8:41, Yuri wrote:
There's comment in slot.c: card_initialize()
/* Always allocate a fixed slot range to one reader/card.
* Some applications get confused if readers pop up in
* different slots. */
Fixed slot range is num_slots from opensc.conf
2007/4/9, Peter Stuge <[EMAIL PROTECTED]>:
On Mon, Apr 09, 2007 at 11:41:50AM +0600, Yuri wrote:
> Why opensc-pkcs11's C_Initialize was done that way? Can you clarify
> commented situation?
A single card can have multiple key pairs and certificates.
PKCS#11 does not permit readers to dynamicall
On 09.04.2007, at 8:41, Yuri wrote:
There's comment in slot.c: card_initialize()
/* Always allocate a fixed slot range to one reader/card.
* Some applications get confused if readers pop up in
* different slots. */
Fixed slot range is num_slots from opensc.conf with default value
On Mon, Apr 09, 2007 at 11:41:50AM +0600, Yuri wrote:
> Why opensc-pkcs11's C_Initialize was done that way? Can you clarify
> commented situation?
A single card can have multiple key pairs and certificates.
PKCS#11 does not permit readers to dynamically change the number of
available slots.
OpenSC
Hi!
I'm going to pay some attention to OpenSC on Win32 platform.
I found strange behaviour of opensc-pkcs11's C_GetSlotList, comparing it to
other pkcs11 implementations.
There's comment in slot.c: card_initialize()
/* Always allocate a fixed slot range to one reader/card.
* Some applica
