Closed
Bug 464717
Opened 16 years ago
Closed 9 years ago
Security Device access on Vista does not work
Categories
(Core :: Security: PSM, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: varga.viktor, Unassigned)
References
()
Details
(Whiteboard: [psm-smartcard])
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; hu; rv:1.9.0.3) Gecko/2008092417 Firefox/3.0.3
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; hu; rv:1.9.0.3) Gecko/2008092417 Firefox/3.0.3
I have found, that the connected security device will not work together with the Firefox, when used on Vista.
The test cases:
1) Oberthur IDONE card, Cardman 3x21, Firefox actual version, Vista
- will not work, doesnot can handle window.crypto.signText
2) Oberthur IDONE card, Cardman 3x21, Firefox actual version, XP
-works with window.crypto.signText
To close out some core functionality, i have checked the Thunderbird to on Vista, and it can encrypt messages.
(Oberthur IDONE card, Cardman 3x21, Thunderbird actual version, Vista)
Error can be at PKCS11 andle or at the window.crypto...
You cantest on the page: https://vny.nive.hu/digitalis_alairas_teszt
Reproducible: Always
Steps to Reproduce:
1. Get a certificate put it on an Oberthur IDONE card
2. Try to use it with Firefox on a window.crypto page.
3. It will fails.
Actual Results:
Fails.
Expected Results:
Should work.
Updated•16 years ago
|
Assignee: nobody → kaie
Component: General → Security: PSM
Product: Firefox → Core
QA Contact: general → psm
Comment 1•14 years ago
|
||
Mass change owner of unconfirmed "Core:Security UI/PSM/SMime" bugs to nobody.
Search for kaie-20100607-unconfirmed-nobody
Assignee: kaie → nobody
Updated•14 years ago
|
Summary: Security Device access on Vista doesnot works → Security Device access on Vista does not work
Whiteboard: [psm-smartcard]
Comment 2•9 years ago
|
||
Thanks for filing the bug. Bug 1030963 removed the window.crypto.signText stuff, so I'm resolving this as "INVALID" in the sense that window.crypto.signText itself is not supposed to work.
You need to log in
before you can comment on or make changes to this bug.
Description
•