Closed Bug 1588531 Opened 3 months ago Closed 3 months ago

[Certificate Viewer] The 'Key Usages Purposes' field is empty

Categories

(Firefox :: Security, defect, P3)

71 Branch
Desktop
All
defect

Tracking

()

VERIFIED FIXED
Firefox 71
Tracking Status
firefox71 --- verified

People

(Reporter: cbaica, Assigned: carolina.jimenez.g)

References

(Blocks 2 open bugs)

Details

Attachments

(1 file)

Affected versions

  • 71.0a1

Affected platforms

  • Windows 10
  • Ubuntu 18.04
  • macOS 10.14

Steps to reproduce

  1. Launch Firefox.
  2. Navigate to badssl.
  3. Click on the 'self-signed' item under Certificate, then Accept the Risk and continue to the page.
  4. View the certificate from the page info panel and look over the displayed elements.

Expected result

  • The Key Usages Purposes field is populated with data.

Actual result

  • The Key Usages Purposes field is empty.

Regression range

  • This is not a regression since it's part of the new feature.

Note

  • If the field is empty it shouldn't be displayed at all or like on other fields just display 'No'.
Blocks: 1553524
Priority: -- → P3

I've notice this occurring on a 'good' certificate as well. You can download that certificate from this link http://www.cacert.org/certs/root_X0F.crt and import in Firefox.

Summary: [Certificate Viewer] The 'Key Usages Purposes' field is empty on a bad certificate → [Certificate Viewer] The 'Key Usages Purposes' field is empty
Assignee: nobody → carolina.jimenez.g
Keywords: checkin-needed

Pushed by rmaries@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/2d7f0b8a65dd
Fixes elements with array sizes equals 0 being rendered and updates test to check non-empty fields being rendered.r=johannh,fluent-reviewers,flod

Keywords: checkin-needed
Status: NEW → RESOLVED
Closed: 3 months ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 71

The issue is verified fixed on the latest Fx71.0a1 nightly build. The empty field is no longer displayed.

Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.