Security/CryptoEngineering/Platform Use of NSS: Difference between revisions

Jump to navigation Jump to search
→‎PKCS#11 XPCOM APIs: add note regarding searching for blank token names
(→‎Remaining Issues: add resolved issues section)
(→‎PKCS#11 XPCOM APIs: add note regarding searching for blank token names)
Line 20: Line 20:


==== PKCS#11 XPCOM APIs ====
==== PKCS#11 XPCOM APIs ====
Currently the platform exposes some PKCS#11 module APIs that include such functionality as getting a handle on the internal module, listing known modules, and searching for modules, tokens, and/or slots. Because the user's software token is now not the same as that returned by PK11_GetInternalKeySlot, these APIs must be special-cased to continue to behave as expected. For example, if the user searches for a module with a blank name, the internal module (as loaded by SECMOD_OpenUserDB) must be returned.
Currently the platform exposes some PKCS#11 module APIs that include such functionality as getting a handle on the internal module, listing known modules, and searching for modules, tokens, and/or slots. Because the user's software token is now not the same as that returned by PK11_GetInternalKeySlot, these APIs must be special-cased to continue to behave as expected. (The issue regarding the undocumented feature of searching for a blank token name returning the internal module has been addressed by [https://bugzilla.mozilla.org/show_bug.cgi?id=1324071 bug 1324071]).


==== FIPS ====
==== FIPS ====
Confirmed users
299

edits

Navigation menu