Closed
Bug 412455
Opened 17 years ago
Closed 17 years ago
Regression, EV UI no longer shows up
Categories
(Core :: Security: PSM, defect)
Core
Security: PSM
Tracking
()
RESOLVED
FIXED
People
(Reporter: KaiE, Assigned: KaiE)
References
Details
(Keywords: regression)
Attachments
(1 file)
7.29 KB,
patch
|
rrelyea
:
review+
mtschrep
:
approval1.9+
|
Details | Diff | Splinter Review |
As noted in bug 406755 comment 11 and 12, bug 406999 caused a regression.
The EV UI (green identity area) no longer shows up.
(This affects only people who were testing EV with the special environment variables set.)
Assignee | ||
Updated•17 years ago
|
Assignee | ||
Comment 1•17 years ago
|
||
Fix in hand. Requesting blocking. I'm surprised I didn't catch this in my testing of bug 406999.
Flags: blocking1.9?
Assignee | ||
Comment 2•17 years ago
|
||
The culprit was my new function hasCertErrors() added in 406999.
I added an incorrect conclusion, the new code says:
"if !mSSLStatus->mHaveCertStatus then the cert is bad"
But I misinterpreted the meaning of variable mHaveCertStatus.
For good certs this variable always remains at false.
Only for certs which receive a "bad cert" callback from NSS this variable might change to true.
The variable should really be named mHaveCertErrorBits.
I propose to rename the variable as part of this fix to avoid future confusion.
Comment 4•17 years ago
|
||
Comment on attachment 297187 [details] [diff] [review]
Patch v1
r+ = rrelyea
Attachment #297187 -
Flags: review?(rrelyea) → review+
Assignee | ||
Comment 5•17 years ago
|
||
Comment on attachment 297187 [details] [diff] [review]
Patch v1
requesting approval.
small change in nsNSSSocketInfo::hasCertErrors(), remainder of patch is a variable rename
Attachment #297187 -
Flags: approval1.9?
Updated•17 years ago
|
Attachment #297187 -
Flags: approval1.9? → approval1.9+
Assignee | ||
Comment 6•17 years ago
|
||
fixed
Status: NEW → RESOLVED
Closed: 17 years ago
Flags: blocking1.9?
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•