Changeset 87d7f89 in mod_gnutls for doc/mod_gnutls_manual.md
- Timestamp:
- Apr 4, 2020, 1:07:28 PM (11 months ago)
- Branches:
- asyncio, master, proxy-ticket
- Children:
- ee35a9f
- Parents:
- e932ba5
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
doc/mod_gnutls_manual.md
re932ba5 r87d7f89 640 640 ### GnuTLSOCSPCheckNonce 641 641 642 Check the nonce in OCSP responses? 642 Send nonces in OCSP requests and verify them in responses. 643 643 644 644 GnuTLSOCSPCheckNonce [On|Off] … … 647 647 Context: server config, virtual host 648 648 649 Most CAs do not to send nonces in their OCSP responses, probably 650 because that way they can cache responses, which is [explicitly 651 allowed by RFC 652 6960](https://tools.ietf.org/html/rfc6960#section-2.5). You can enable 653 `GnuTLSOCSPCheckNonce` to enforce nonce validation if your CA is one 654 that supports OCSP nonces. Note that `mod_gnutls` will _send_ a nonce 655 either way. 649 If `GnuTLSOCSPCheckNonce` is enabled, `mod_gnutls` will send nonces in 650 OCSP requests and verify them in responses. Responses without a nonce 651 or with a mismatching one will be considered invalid and discarded. 652 653 This option is disabled by default because many CAs do not support the 654 OCSP nonce extension. The likely reason for that is the use of 655 pre-produced responses, as described in [RFC 6960, Section 656 2.5](https://tools.ietf.org/html/rfc6960#section-2.5). 656 657 657 658 ### GnuTLSOCSPResponseFile
Note: See TracChangeset
for help on using the changeset viewer.