Closed Bug 490458 Opened 17 years ago Closed 10 years ago

Imprecise error message when loading a new PKCS11 module fails

Categories

(Core :: Security: PSM, defect)

x86
macOS
defect
Not set
normal

Tracking

()

RESOLVED WONTFIX

People

(Reporter: te.mlists, Unassigned)

Details

(Whiteboard: [psm-smartcard][psm-feedback])

User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_5_6; de-de) AppleWebKit/525.27.1 (KHTML, like Gecko) Version/3.2.1 Safari/525.27.1 Build Identifier: 2.0.0.16 Steps to reproduce Reproducible: Always Steps to Reproduce: 1. Choose Preferences > Encryption > Security Devices > Load… 2. Enter the path to your PKCS#11 module, don't use browse, hit OK Actual Results: Error message "Loading of Module XXXX failed" Expected Results: When loading fails, a helpful user message e.g. - opening the library failed (dyld error XXXX) - resolving PKCS11 entry points failed (bogous library) - initialisation failed with error XXXX (i.e there is no attached slot when C_Initialize is called) I've seen many "non-admin-type" users that do not expect the loading of the library failing when - according to the PKCS spec - C_Initialize fails due to an missing slots. The current behavior is inconsistend: - you can not load a module that fails to init correctly - however, once init'ed, it will remain in the security module list regardless if the init call fails or not. Sidenote: Also applies to FireFox
As this seems to apply to firefox as well, therefore moving to the core component where most of these bugs go.
Assignee: nobody → kaie
Component: Security → Security: PSM
Product: Thunderbird → Core
QA Contact: thunderbird → psm
Mass change owner of unconfirmed "Core:Security UI/PSM/SMime" bugs to nobody. Search for kaie-20100607-unconfirmed-nobody
Assignee: kaie → nobody
Whiteboard: [psm-smartcard][psm-feedback]
This would require considerable effort for something that only a fraction of users do very rarely.
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.