Closed Bug 1300150 Opened 8 years ago Closed 2 years ago

fix ccadb2OneCRL so it doesn't incorrectly drop leading zeroes from serial numbers

Categories

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

defect

Tracking

()

RESOLVED FIXED

People

(Reporter: mgoodwin, Unassigned)

References

Details

(Keywords: stale-bug, Whiteboard: [ca-onecrl] [psm-backlog])

Kathleen observed that sometimes the serial number data in a CRL differs from the serial number data in the certificate being revoked. Both of these can be valid (and refer to the same serial number), yet OneCRL will currently treat them as being different (resulting in possible false negatives in OneCRL checks).

We should fix this.
Summary: Modify OneCRL serial numbers to allow leading zeros → Modify OneCRL serial number parsing to allow leading zeros
Priority: -- → P1
Whiteboard: [psm-assigned]
Priority: P1 → P2
Whiteboard: [psm-assigned] → [psm-backlog]

The bug assignee didn't login in Bugzilla in the last months and this bug has priority 'P2'.
:keeler, could you have a look please?
For more information, please visit auto_nag documentation.

Assignee: bugs → nobody
Flags: needinfo?(dkeeler)
Whiteboard: [psm-backlog] → [ca-onecrl] [psm-backlog]

Hopefully fixing this bug would prevent bugs like Bug #1717100 from occurring.

Severity: normal → S4
Flags: needinfo?(dkeeler)
Priority: P2 → P3
Summary: Modify OneCRL serial number parsing to allow leading zeros → fix ccadb2OneCRL so it doesn't incorrectly drop leading zeroes from serial numbers
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.