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

Jump to bottom

x/crypto/ocsp: Certificate Transparency, Stapled SCTs #13297

Closed
mehmooda opened this issue Nov 17, 2015 · 3 comments
Closed

x/crypto/ocsp: Certificate Transparency, Stapled SCTs #13297

mehmooda opened this issue Nov 17, 2015 · 3 comments
Labels
FrozenDueToAge

Comments

@mehmooda
Copy link

Support for Stapling SignedCertificateTimestamps would be nice:

To implement:

  • RFC6960 Single Response Extensions EASY. crypto.pkix.Extension
  • RFC6962 Certificate Transparency OCSP MEDIUM
@bradfitz
Copy link
Contributor

/cc @agl

@agl
Copy link
Contributor

agl commented Nov 18, 2015

SCTs via the TLS handshake are already supported. At some point it'll make sense to also support validation of SCTs and thus embedded SCTs in certificates and stapled OCSP responses. But I don't think that time is yet as Chrome is still developing this and Go clients aren't the best early use-case for CT.

@agl agl closed this as completed Nov 18, 2015
@mehmooda
Copy link
Author

I should have probably created 2 issues. What is required in go is only extension support.

SCTs can be provided by another package at least for now.

All that is required to support extensions is:
https://go-review.googlesource.com/#/c/16946/

@golang golang locked and limited conversation to collaborators Nov 17, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
FrozenDueToAge
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@bradfitz @agl @mehmooda @gopherbot