On Thu, 18 Dec 2014, Jaroslav Imrich wrote: >> >> removable token and you cannot use slot-description, slot-manufacturer >> and >> >> neither of token attributes? So the only option left is: >> pkcs11:slot-id=2 >> >> ??? >> > >> >I think so. This is really for Jan to answer. Maybe the Solaris >> >libpkcs11 should just ensure a meaningful (stable and distinct) slot >> >label. If that could be done then slot-id could be excluded here. >> > >> >Jan? >> >> for example, metaslot on Solaris is always 0 so slot-id=0 >> would be reliable there to use to access the soft token. Jan. > >And there is no other URI that could identify that slot without the slot-id >attribute? i.e. pkcs11:slot-description=metaslot hi Jaroslav, you could use the slot description to find the slot but that's not the case. The thing is that you can use slot 0 reliably there so slot-id would make sense in that context. We have attributes that can be reasonable used only in certain scenarios and not others, like "pin-value". Jan. -- Jan Pechanec <jan.pechanec@xxxxxxxxxx>