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

OCSP Stapling #43

Open
Nothing4You opened this issue Apr 16, 2015 · 7 comments
Open

OCSP Stapling #43

Nothing4You opened this issue Apr 16, 2015 · 7 comments

Comments

@Nothing4You
Copy link

Please implement OCSP Stapling.
This is especially useful to 1. reduce load of OCSP servers and 2. prevent privacy leaks of who is connecting to your host towards the OCSP server.

@biergaizi
Copy link

+1.

@robert-scheck
Copy link
Contributor

Any chance?

@brunoos
Copy link
Member

brunoos commented Feb 8, 2018

I don't know how hard is to implement this.
I'm focused on university stuffs, I need to find free time for it.

@mimi89999
Copy link

Hello,
Are there any news on this?

@brunoos
Copy link
Member

brunoos commented Jun 16, 2021

Sorry, I confess I did not look anything about it. I will try to find time to see it.

@Zash
Copy link
Contributor

Zash commented Jun 16, 2021

I started some exploratory coding in https://github.com/Zash/luasec/tree/ocsp that I believe manages a partial client-side OCSP check. No idea how to do the server-side parts yet, or how to check the cert for the must-staple flag.

@WhyNotHugo
Copy link

WhyNotHugo commented Dec 10, 2024

ocspcheck from openbsd fetches an ocsp response and can save it into a file. httpd can be configured to read these pre-fetched ocsp responses and stamp them.

Its source might be a useful reference: https://github.com/openbsd/src/tree/master/usr.sbin/ocspcheck

It's also possible to follow a similar design, where the OCSP response is read from the file and stamped into responses, without having to re-implement fetching them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

7 participants