Skip to content

ocsp: reject ocsp responses where version is not v1 #20096

@zuercher

Description

@zuercher

See #20079. In the event that updates to the OCSP specification are released and the OCSP response version is incremented, Envoy would currently accept the new data but might not correctly parse or interpret it. Envoy should explicitly reject versions other than v1 (a value of 0).

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions