487854 - Installing Litronic PKCS11 (x64) into Security Devices fails - reports the module has loaded successfully

Status: RESOLVED INCOMPLETE

(Core :: Security: PSM, defect)

Description

[jet]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.0 x64; en-US; rv:1.9.2a1pre) Gecko/20090404 Minefield/3.6a1pre
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0 x64; en-US; rv:1.9.2a1pre) Gecko/20090404 Minefield/3.6a1pre

Install LitPKCS11 (x64) into Tools > Options > Advanced > Security Devices 
MineField reports the module has loaded successfully. 
In the MineField Device Manager I can see all Smart Card Reader attached to the system, but can't get at the Smart Cards inserted in the readers

Add-on > Extensions reports the PKCS11 extension as not compatible with MineField version 3.6a1pre
If I log on as another user LitPKCS11 is no longer installed in Security Devices, but is still reported as not supported in Add-On Extensions.


Reproducible: Always

Steps to Reproduce:
1.Open Tools > Options > Advanced > Security Devices 
2.Select > Load
3.Select > 3rd party Module
4.Select > OK

Actual Results:  
Application reports success 
Smart Card readers can be seen 
Smart Cards can not be accessed

Expected Results:  
Smart Cards can be accessed 
3rd party extension can be accessed in the Add-On extension view

Not sure if we are hung up between x86 and x64 but when I tried to load the x86 version it failed and was correctly reported as failing

Comment 1

[jet]

Attachment: Extension Add-On and Security Devices showing SCReaders

Comment 2

[Daniel Veditz [:dveditz]]

Until we know otherwise let's just stick to the facts you know: LitPKCS11 doesn't work, other 3rd-party modules may or may not work.

Does the fact that the addon is disabled have any bearing here? The addon might just be a packaging mechanism for the PKCS11 module, or there might be real code in there that the module needs to function correctly.

What versions does that addon claim to support? Have you tried it in those versions? (e.g. Firefox 3.0 or 3.5?)

If you make the risky assumption that the addon is just a packaging scheme and isn't really incompatible, what happens if you manually tweak compatibility checking (either by disabling the checks in Firefox or tweaking the version range in the extension)--does it start working or does it still fail? Fail differently?

At this point it's hard to say if it's a problem with the addon or in Firefox. Or if you just need technical support on how to get addons to work with non-official builds.

Comment 3

[Kai Engert (:KaiE:)]

Mass change owner of unconfirmed "Core:Security UI/PSM/SMime" bugs to nobody.
Search for kaie-20100607-unconfirmed-nobody

Comment 4

[Dana Keeler (she/her) (use needinfo) [:keeler] (on leave)]

Please see comment 2.