bogous ocsp response not updated #509

Closed
opened 2025-12-29 01:26:28 +01:00 by adam · 1 comment
Owner

Originally created by @bjacke on GitHub (Dec 3, 2020).

currently letsencrypt has an issue to deliver the correct oscp response after a certificate was issued. dehydrated returns in such cases:

  • Updating OCSP stapling file
    OCSP single response: Certificate ID does not match any certificate or issuer.

if you run dehydrated after that again it does not see, that the ocsp resonse is invalid and should be updated:

  • OCSP stapling file is still valid (skipping update)

It shoud see that the ocsp response does not match the current certificate and try to fetch a valid resonse instead.

Originally created by @bjacke on GitHub (Dec 3, 2020). currently letsencrypt has an issue to deliver the correct oscp response after a certificate was issued. dehydrated returns in such cases: + Updating OCSP stapling file OCSP single response: Certificate ID does not match any certificate or issuer. if you run dehydrated after that again it does not see, that the ocsp resonse is invalid and should be updated: + OCSP stapling file is still valid (skipping update) It shoud see that the ocsp response does not match the current certificate and try to fetch a valid resonse instead.
adam closed this issue 2025-12-29 01:26:28 +01:00
Author
Owner

@bjacke commented on GitHub (Dec 10, 2020):

sorry, it turned out that this was a haproxy ocsp problem here, dehydrated is actually doing everything right here and checks that the ocsp response is the right one.

@bjacke commented on GitHub (Dec 10, 2020): sorry, it turned out that this was a haproxy ocsp problem here, dehydrated is actually doing everything right here and checks that the ocsp response is the right one.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/dehydrated#509