Closed
Bug 708211
Opened 13 years ago
Closed 9 years ago
[10.7] cannot establish ssl "with SmartCard" by 64bit firefox
Categories
(Core :: Security: PSM, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: liero27, Unassigned, NeedInfo)
References
(Blocks 1 open bug)
Details
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:7.0) Gecko/20100101 Firefox/7.0
Build ID: 20110916091512
Steps to reproduce:
I am a PKCS#11 developer. I moved my source code to MacOS from Windows platform, and compiled it both with -arch x86_64 and i386 flags.
everything works fine under Windows, old versions of Mac OS (32 bit) and under new one with swithed on 32bit compatibility mode flag in Firefox.
All functionality works fine under x86_64 (Signig, importing certificates, etc) when we use PKCS from our own applications
Actual results:
but under 64 bit Firefox (seccurity devices has been added successfully, and I can log in to Card via firefox). When try to establish ssl connection, firefox shows the ssl error even before show certificate !!!.
I have checked more than once, and I am pretty sure that all values returned form my PKCS#11 to browser (f.e. from methods: C_FindObjects, C_GetAttributeValue) are exactly the same under Windows or 32 bit MacOS (where works fine) and 64 bit (where the problem occures).
Expected results:
My first question is if 64 bit firefox on Mac OS X 10.7 works correctly with any one PKCS#11 without compatibility mode??
I belive that FireFox behavior should be the same irrespective of architecture.
Updated•13 years ago
|
Summary: [Mac OS X 10.7]cannot establish ssl "with SmartCard" by 64bit firefox → [10.7] cannot establish ssl "with SmartCard" by 64bit firefox
Updated•13 years ago
|
Component: Security → Security: PSM
Product: Firefox → Core
QA Contact: firefox → psm
Updated•13 years ago
|
Blocks: lion-compatibility
Comment 1•11 years ago
|
||
Is this actually a 10.7 bug or unrelated to the OS version?
Updated•9 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•