On 1/1/09, Martin Paljak wrote:
> > %% Here you can see that two applications may sign, even one
> > application may delete the key at the same time the other application
> > sign using it... How can it be if both applications cannot
> > authenticate at the same time?
> >
>
> I'm not just
On 30.12.2008, at 21:28, Alon Bar-Lev wrote:
> On 12/30/08, Martin Paljak wrote:
>>
>>> The PKCS#11 specification does not limit concurrent application
>>> access
>>> to single token in any point in time.
>>> The lock term was introduced by OpenSC due to implementation choice.
>> At the same t
On 12/30/08, Martin Paljak wrote:
> On 29.12.2008, at 20:48, Alon Bar-Lev wrote:
> > On 12/29/08, Martin Paljak wrote:
> > > On 27.12.2008, at 22:18, Alon Bar-Lev wrote:
> > > > Until we do so, the PKCS#11 provider is *NOT* compliant with the
>> > > specification.
> > > Please elaborate?
> > The
On 29.12.2008, at 20:48, Alon Bar-Lev wrote:
> On 12/29/08, Martin Paljak wrote:
>>
>> On 27.12.2008, at 22:18, Alon Bar-Lev wrote:
>>
>>
>>> Until we do so, the PKCS#11 provider is *NOT* compliant with the
>> specification.
>>>
>>
>> Please elaborate?
>
> The PKCS#11 specification does not limi
On 12/29/08, Martin Paljak wrote:
>
> On 27.12.2008, at 22:18, Alon Bar-Lev wrote:
>
>
> > Until we do so, the PKCS#11 provider is *NOT* compliant with the
> specification.
> >
>
> Please elaborate?
The PKCS#11 specification does not limit concurrent application access
to single token in any po
On 27.12.2008, at 22:18, Alon Bar-Lev wrote:
> Until we do so, the PKCS#11 provider is *NOT* compliant with the
> specification.
Please elaborate?
--
Martin Paljak
http://martin.paljak.pri.ee
+372.515.6495
___
opensc-devel mailing list
opensc-d
Yes, we discussed this many times.
We should work in order to make opensc stateless, and allow concurrent
application usage.
Until we do so, the PKCS#11 provider is *NOT* compliant with the specification.
Alon.
On 12/27/08, Andreas Jellinghaus wrote:
> oops, lock_login is off by default?
> and
oops, lock_login is off by default?
and my standard test procedure doesn't event work
in that situation at all (init, create pin, create key,
create self-signed cert, store cert, run test procedures ...
all with egate+cryptoflex 32k).
not sure how many times we discussed it already, and
not even s
