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.

Sign up for GitHub

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

Support OCSP stapling #18

Closed
colmmacc opened this issue Sep 2, 2014 · 2 comments · Fixed by #57
Closed

Support OCSP stapling #18

colmmacc opened this issue Sep 2, 2014 · 2 comments · Fixed by #57
Assignees
@baldwinmatt

Comments

@colmmacc
Copy link
Contributor

colmmacc commented Sep 2, 2014

s2n should support OCSP stapling. Implementing HTTP and calling an OSCP endpoint is likely overkill, but it should at least be possible for the caller to periodically provide an OCSP token.
@baldwinmatt baldwinmatt self-assigned this Feb 25, 2015
@baldwinmatt
Copy link
Contributor

I have request/response implemented.

next up is validating the status

@baldwinmatt
Copy link
Contributor

This requires some thought. As a client, we should give the application notice that OCSP validation failed, and allow the user/programmer to make a decision on what to do next.

For now, I'll implement an API to retrieve the OCSP response.

@baldwinmatt baldwinmatt mentioned this issue Mar 3, 2015
Merged
baldwinmatt added a commit that referenced this issue Jun 29, 2015
@baldwinmatt
Add OCSP stapling request support.
284562d 
This commit adds an API to s2n which enables the client to request an OCSP
ticket from the server when handshaking.

works towards: #18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@baldwinmatt baldwinmatt

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add support for OCSP requests and responses
2 participants
@colmmacc @baldwinmatt