Closed
Bug 255140
Opened 20 years ago
Closed 8 years ago
Allow access to certificates rejected by NSS
Categories
(Core Graveyard :: Security: UI, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 943937
People
(Reporter: timeless, Unassigned)
References
()
Details
We need to visit jpmorgan.com
Unforunately, mozilla helpfully refuses to allow such a visit saying:
Could not establish an encrypted connection because certificate presented by
mm.jpmorgan.com is invalid or corrupted. Error Code: -8101
(bug 255136)
At the very least, I should be able to click a button or widget and view the cert.
i shouldn't have to pull out my debugger, a copy of lxr, and the nss reference
in order to find out precisely how the certificate was misconfigured.
Note: IE will connect to that server, and is immediately wisked away to yet
*another* server.
Comment 1•20 years ago
|
||
I suppose this is a bug at the NSS SSL level.
Assignee: kaie → wtchang
Component: Client Library → Build
Product: PSM → NSS
QA Contact: wtchang
Comment 2•20 years ago
|
||
As listed here
http://www.mozilla.org/projects/security/pki/nss/ref/ssl/sslerr.html
-8101 means:
SEC_ERROR_INADEQUATE_CERT_TYPE
Updated•19 years ago
|
Assignee: wtchang → nobody
QA Contact: wtchang → build
Comment 3•18 years ago
|
||
This bug is asking for improved UI in an error case. NSS doesn't do UI.
Assignee: nobody → nobody
Blocks: 107491
Component: Libraries → Build Config
Product: NSS → Core
QA Contact: libraries → build-config
Version: unspecified → 1.8 Branch
first, kaie: i was well aware of that when i filed the bug note the specific other bug referenced in it.
nelson: fair enough. are you sure that the certificate for the site is available for psm to display? and that psm can actually figure out what's wrong from what nss has told it?
Assignee: nobody → kengert
Component: Build Config → Security: UI
QA Contact: build-config
Summary: Allow access to ceritificates rejected by NSS → Allow access to certificates rejected by NSS
Updated•18 years ago
|
QA Contact: ui
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
Assignee | ||
Updated•8 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•