On 9/26/07, Robert Relyea <[EMAIL PROTECTED]> wrote: > > Currently there are really only 3 errors that a PKCS #11 module can > return when it's having internal problems (that is errors that are > independent of the caller's usage): CKR_FUNCTION_FAILED, > CKR_GENERAL_ERROR, CKR_DEVICE_ERROR. > > Typically softoken treats errors in freebl (that can't otherwise be > identified) as 'device errors' (consistent with what hardware PKCS #11 > modules would return if, say, the internal key was corrupted or something. > > We do turn NSS specific errors in the case of failing to initialize the > database, we could probably define an error that says 'failure to load > freebl', which is the most common reason for CKR_DEVICE_ERROR from that > level.
I suspect that a missing libfreebl3.so won't prevent NSS from initializing the database because libfreebl3.so is dynamically loaded the first time we use it. Unless we need to perform crypto operations when initializing the database, we won't load libfreebl3.so and therefore won't detect its absence. Wan-Teh _______________________________________________ dev-tech-crypto mailing list dev-tech-crypto@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-tech-crypto
