Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

x/crypto/ocsp: Should include responderID in parsed Responses #14971

Closed
jsha opened this issue Mar 26, 2016 · 1 comment
Closed

x/crypto/ocsp: Should include responderID in parsed Responses #14971

jsha opened this issue Mar 26, 2016 · 1 comment
Assignees
Milestone

Comments

@jsha
Copy link

@jsha jsha commented Mar 26, 2016

Per RFC 6960, ResponseData includes ResponderID. It's useful for clients to be able to validate ResponderID against the issuer certificate they are expecting. The Response type should include this field (which may be composite), and ParseResponse should fill it and validate it if provided with an issuer certificate.

@bradfitz bradfitz changed the title ocsp: Should include responderID in parsed Responses x/crypto/ocsp: Should include responderID in parsed Responses Apr 9, 2016
@bradfitz bradfitz added this to the Unreleased milestone Apr 9, 2016
@agl agl self-assigned this Aug 19, 2016
@gopherbot
Copy link

@gopherbot gopherbot commented Dec 14, 2016

CL https://golang.org/cl/34380 mentions this issue.

@golang golang locked and limited conversation to collaborators Dec 21, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants
You can’t perform that action at this time.