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

nghttpx: Verify OCSP response #929

Merged
merged 2 commits into from
May 25, 2017
Merged

nghttpx: Verify OCSP response #929

merged 2 commits into from
May 25, 2017

Conversation

tatsuhiro-t
Copy link
Member

At least we should make sure that the OCSP response is targeted to the
expected certificate. This is important because we pass the file path
to the external script, and if the file is replaced because of
renewal, and nghttpx has not reloaded its configuration, the
certificate nghttpx has loaded and the one included in the file
differ. Verifying the OCSP response detects this, and avoids to send
wrong OCSP response.

At least we should make sure that the OCSP response is targeted to the
expected certificate.  This is important because we pass the file path
to the external script, and if the file is replaced because of
renewal, and nghttpx has not reloaded its configuration, the
certificate nghttpx has loaded and the one included in the file
differ.  Verifying the OCSP response detects this, and avoids to send
wrong OCSP response.
@tatsuhiro-t tatsuhiro-t added this to the v1.23.0 milestone May 25, 2017
@tatsuhiro-t tatsuhiro-t merged commit 74c2f12 into master May 25, 2017
@tatsuhiro-t tatsuhiro-t deleted the nghttpx-verify-ocsp branch May 25, 2017 14:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant