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 the meeting in
which
we discussed this. The original agreement was that removal was
forbidden. Unfortunately the current spec does not forbid removing
slots.
Bob, as you may know, the PKCS#11 working group will be meeting by
telephone
Thursday morning at 6 AM Pacific Time. This seems like a good issue
to
raise in that call. SEED will also be discussed in that call.
What kind of working group? Mozilla centric or some generic? If there
is anything else I could provide before that time or clarifications
needed, let me know. If it is a "public" meeting I could as well call
too if required.
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 with shrinking sets of slots. I think it was simply that if
the
module can shrink it while it is in use, it may cause the code outside
the module to reference a stale pointer. Something like that.
Do you recall the particulars?
How many slots does FF/NSS support (if I need to add new slots with
every different reader for 2 days, when will I run out of slots..)
--
Martin Paljak
http://martin.paljak.pri.ee
+372.515.6495
_______________________________________________
dev-tech-crypto mailing list
dev-tech-crypto@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-tech-crypto
