Open Bug 987426 Opened 12 years ago Updated 2 years ago

NSS OCSP decoding doesn't handle unknown critical extensions

Categories

(NSS :: Libraries, defect, P5)

Tracking

(Not tracked)

People

(Reporter: keeler, Unassigned)

Details

(Whiteboard: [nss-nofx])

The spec says extensions should be marked non-critical, but it also seems to indicate that responses with unknown critical extensions must be ignored.
(In reply to Dana Keeler (:keeler) from comment #0) > The spec says extensions should be marked non-critical, but it also seems to > indicate that responses with unknown critical extensions must be ignored. Unknown critical extensions must NOT be ignored. Instead, they must cause processing to fail. That is the purpose of the critical bit.
Severity: normal → S3

Dana, can you please set Priority and Severity on this bug ?

Flags: needinfo?(dkeeler)
Severity: S3 → S4
Flags: needinfo?(dkeeler)
Priority: -- → P5
Whiteboard: [nss-nofx]
You need to log in before you can comment on or make changes to this bug.