clients like mozilla.
You have to enter the name or the path to a pkcs#11 library. So little Joe User has to care about this stuff.
If you want to use several different pkcs#11 libraries even that has to be managed by the client.
What do you think about the idea to write one pkcs#11 library that is delivered with he os and always installed in a certain spot or at least where it will be found as a library and always with the same name.
This library is only a wrapper to the real pkcs#11 libraries you have. In a config file you define what real pkcs#11 libraries you use and where they are. The wrapper then unifies all those libraries and shows all slots and tokens together.
The advantage would be that the user does not have to configure each client but only one system config file. You could even provide a system like in pcsc-lite where a manufacturer driver only needs to be installed inside a driver directory to be found.
So you have one pkcs#11 rpm that installs to a defined location and token drivers that are installed into subdirectories. This way we have a zero configuration environment like in pc/sc lite (at least with USB;-).
Perhaps the muscle or opensc pkcs#11 library could provide this function.
best regards,
Christian Schneider
_______________________________________________ Muscle mailing list [EMAIL PROTECTED] http://lists.drizzle.com/mailman/listinfo/muscle
