Unfortunately the softoken needs the database configuration information in order to operation. I've been meaning to pick some 'defaults', or pull them out of the environment if the parameter strings are not provided, but haven't had time.
If you wanted to provide changes where softoken would look at an environment variable if the parameter strings have not been provided, I would be happy to include them in NSS. If you are writting an application, I posted how the parameters are supposed to be passed through the INIT_ARGs of C_Initialize, though this is a proposed amendment to the PKCS #11 standard, which has not been adopted yet. That posting was several months ago, so you would have to search the archives. That doc should be part of the NSS 3.4 documentation when it's released. bob Kenneth R. Robinette wrote: > What is the "correct" method of using the new softokn3.dll as a unique > software token? I see where you can modify the pkcs11.c module to add your > own logic in the function nsc_CommonInitialize, to point to the desired > databases, change the token name, etc. but is this the preferred method? > Since the C_Initialize function is already contained within pkcs11.c, I > don't see a way to do so without modifying pkcs11.c itself. > > Ken > > > >
