Robert Relyea wrote, On 2008-12-10 17:12:
> Nelson B Bolyard wrote:
>> I think you're talking about a common implementation where the token and
>> reader are one and the same, and the act of connecting the token also
>> connects a new reader. One way to implement that in PKCS#11 is to add a
>> slo
Nelson B Bolyard wrote:
Firefox does not allow removal. It'll be a small change to the code
to handle removal, though it makes the slot checks more expensive.
If you could write a bug up I'd appreciate it.
I don't recall the details now, but as I recall, there was some nasty
problem
Martin Paljak wrote, On 2008-12-10 03:50:
> On 10.12.2008, at 8:08, Nelson Bolyard wrote:
>> Robert Relyea wrote:
>>> Martin Paljak wrote:
Thanks for tips! Could you point me to the line in spec where it
says that slots can only be added. I cant find the place where it
forbids remo
On 10.12.2008, at 8:08, Nelson Bolyard wrote:
Robert Relyea wrote:
Martin Paljak wrote:
Thanks for tips! Could you point me to the line in spec where it
says
that slots can only be added. I cant find the place where it
forbids
removing.
That's what I get for not checking the spec after th
On 09.12.2008, at 22:17, Robert Relyea wrote:
Martin Paljak wrote:
Thanks for tips! Could you point me to the line in spec where it says
that slots can only be added. I cant find the place where it forbids
removing.
That's what I get for not checking the spec after the meeting in
which we d
Robert Relyea wrote:
> Martin Paljak wrote:
>> Thanks for tips! Could you point me to the line in spec where it says
>> that slots can only be added. I cant find the place where it forbids
>> removing.
>>
> That's what I get for not checking the spec after the meeting in which
> we discussed th
Martin Paljak wrote:
Thanks for tips! Could you point me to the line in spec where it says
that slots can only be added. I cant find the place where it forbids
removing.
That's what I get for not checking the spec after the meeting in which
we discussed this. The original agreement was that
Thanks for tips! Could you point me to the line in spec where it says
that slots can only be added. I cant find the place where it forbids
removing.
On 12/5/08, Robert Relyea <[EMAIL PROTECTED]> wrote:
> Martin Paljak wrote:
>> Thanks!
>>
>> I was only trying to figure out if there is any differe
Martin Paljak wrote:
Thanks!
I was only trying to figure out if there is any difference in 2.11 vs
2.20 handling.
2.20 allows slots to be added during the lifetime of a cryptoki
application.
Can you also explain how NSS handles the feature or any gotchas in
implementing support for hotplugg
Thanks!
I was only trying to figure out if there is any difference in 2.11 vs
2.20 handling.
2.20 allows slots to be added during the lifetime of a cryptoki
application.
Can you also explain how NSS handles the feature or any gotchas in
implementing support for hotpluggable PC/SC readers?
Martin Paljak wrote, On 2008-12-05 07:03:
> Hi!
>
> PKCS#11 modules advertise its versions in two different places: in the
> structure returned by C_GetFunctionList and in C_GetInfo. What happens
> if those versions mismatch or which one has higher priority?
Answering only for NSS,
NSS igno
11 matches
Mail list logo
