Closed Bug 412455 Opened 17 years ago Closed 17 years ago

Regression, EV UI no longer shows up

Categories

(Core :: Security: PSM, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: KaiE, Assigned: KaiE)

References

Details

(Keywords: regression)

Attachments

(1 file)

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.)
Blocks: evtracker, 406755
Depends on: 406999
Fix in hand. Requesting blocking. I'm surprised I didn't catch this in my testing of bug 406999.
Flags: blocking1.9?
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.
Attached patch Patch v1Splinter Review
Proposed fix
Attachment #297187 - Flags: review?(rrelyea)
Comment on attachment 297187 [details] [diff] [review] Patch v1 r+ = rrelyea
Attachment #297187 - Flags: review?(rrelyea) → review+
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?
Attachment #297187 - Flags: approval1.9? → approval1.9+
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.

Attachment

General

Created:
Updated:
Size: