Welcome! Log In Create A New Profile

Advanced

"ssl_stapling" without configured "resolver" caches responder IP indefinitely

January 28, 2022 01:17PM
Hi, while testing the latest NGINX source code around ~1.21.7, I’ve observed that enabling "ssl_stapling" without configuring a “resolver”, makes NGINX cache the OCSP responder IP indefinitely, so, if the CA later changes the OCSP responder IP, NGINX is still going to try to get OCSP queries from the old IP (possibly inoperative now), irrespective of the DNS record TTL.

Now, I'm aware of https://nginx.org/en/docs/http/ngx_http_ssl_module.html#ssl_stapling saying:

> For a resolution of the OCSP responder hostname, the resolver directive should also be specified.

And effectively, using the “resolver” directive, OCSP DNS records are refreshed, but it is not obvious at all what is going to happen if a "resolver" is not configured. Is there any documentation on this? Additionally, what is the reason to not use the default system DNS resolvers in the standard way (i.e. respecting DNS TTLs) instead of performing the resolution only once when no "resolver" is configured?
Subject Author Posted

"ssl_stapling" without configured "resolver" caches responder IP indefinitely

hablutzel1 January 28, 2022 01:17PM

Re: "ssl_stapling" without configured "resolver" caches responder IP indefinitely

Maxim Dounin January 28, 2022 05:10PM

Re: "ssl_stapling" without configured "resolver" caches responder IP indefinitely

hablutzel1 January 28, 2022 09:29PM

Re: "ssl_stapling" without configured "resolver" caches responder IP indefinitely

Sergey A. Osokin January 28, 2022 10:08PM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 132
Record Number of Users: 8 on April 13, 2023
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready