Closed
Bug 1073042
Opened 11 years ago
Closed 10 years ago
signing a transaction in a webpage with a certificate
Categories
(Firefox :: Untriaged, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: msiroit, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:33.0) Gecko/20100101 Firefox/33.0
Build ID: 20140923222114
Steps to reproduce:
I tried to sign with a certificate a transaction in a webpage using Firefox Beta 33.
Actual results:
It doesn't event bring up the certificate, and gives the server an empty response
Expected results:
It should bring up the option to let me choose which certificate should I use to sign that transaction. And then respond the server with the certificate to be able to sign
Updated•11 years ago
|
Group: core-security
Updated•11 years ago
|
Summary: siging → signing a transaction in a webpage with a certificate
well, OK, looks like api was changed in 33, so this is not bug...
I just received recommendation from bank to use ESR until they'll rewrite there software. Also, as I see in changelogs, change is documented at least in 33 beta relase notes from Sept 2.
This IS a bug, I am using certificates that are not self signed, they belong to intermediate certificate authorities recognized by VeriSign. While trying to get the certificate for signing a transaction on the page, I get no option to choose, and the page receives nothing, this means Firefox is not providing any chance of bringing the certificate to the server
Please retest this issue with the latest version of Firefox (https://www.mozilla.org/en-US/firefox/new/). If you are still having this issue, please provide the exact steps and some links we could test this with.
Thank you.
Flags: needinfo?(msiroit)
Hi.
Marking this as Resolved: Incomplete due to the lack of response from the reporter.
Reporter, please feel free to reopen it if you are still having this issue.
Thank you for your time.
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Flags: needinfo?(msiroit)
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•