Closed Bug 754369 Opened 13 years ago Closed 2 years ago

SSL Status is not always constructed before we call the bad cert handler or the SSL error listener

Categories

(Core :: Security: PSM, defect, P5)

Product:
Core
Component:
Security: PSM
Type:
defect

Tracking

()

Status:
RESOLVED DUPLICATE of bug 1550686

People

(Reporter: briansmith, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: regression, Whiteboard: [psm-backlog])

+++ This bug was initially created as a clone of Bug #739563 +++ +++ This bug was initially created as a clone of Bug #739558 +++ PSM has a bug where it does not set the SSLStatus of the socket before calling the SSL error listener. The patches that are coming for bug 754365 should fix this.
bsmith, would this fix Bug 739558 and similar "failing silently" bugs?
Nope, but Thunderbird bug 739563 and the other Firefox bug would.
I have a whole series of patches written for bug 754365, which happen to fix this bug, and which are needed for other important work. So, I am going to finalize the series of patches for bug 754365 and submit them for review, and then I'm going to keep this bug open for the tests that verify that the nsISSLStatus object is passed to the nsISSLErrorListener.
Assignee: nobody → bsmith
bsmith writes in bug 785426 comment 57: > nsISSLErrorListener .. socketInfo ... getInterface() ... nsITransportSecurityInfo.errorMessage > ... your application can strip the HTML tags from the ... formatted-for-Firefox error message
Assignee: brian → nobody

bug 1550686 removed nsIBadCertListener2 and bug 844351 removed nsISSLErrorListener.

Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.