> > But why don't you store the needed SM-data in the card's
> > private data? This way each card handle has it's own SM context and
> > could access the card with different SM parameters (if supported).
>
> Sorry I can't: AFAIK DNIe is "read only", at least at user level
> Ideally, virtual channe
El jue, 17-02-2011 a las 16:50 +0100, Frank Morgner escribió:
> On Monday, February 14 at 12:22PM, jons...@terra.es wrote:
> > In the testing process of OpenDNIe I've found a problem related with
> > concurrent
> > access to opensc-pkcs11 library.
(from a previous mail from Douglas)
> Does the ca
On Monday, February 14 at 12:22PM, jons...@terra.es wrote:
> In the testing process of OpenDNIe I've found a problem related with
> concurrent
> access to opensc-pkcs11 library.
>
> In short: as DNIe can only handle one SM at a time (no virtual channel
> support),
> there is no (known) way to g
On 2/14/2011 5:22 AM, jons...@terra.es wrote:
> In the testing process of OpenDNIe I've found a problem related with
> concurrent
> access to opensc-pkcs11 library.
>
> In short: as DNIe can only handle one SM at a time (no virtual channel
> support),
> there is no (known) way to get concurrent
In the testing process of OpenDNIe I've found a problem related with concurrent
access to opensc-pkcs11 library.
In short: as DNIe can only handle one SM at a time (no virtual channel
support),
there is no (known) way to get concurrent pkcs11 access
This "feature" makes unusable most of signin
