Move the OCSP change to the right section. (#6818)

Looks like this got added to our changelog for the released 0.31.0 instead of the upcoming release. We want this change for the release tomorrow.
This commit is contained in:
Brad Warren 2019-03-05 14:01:08 -08:00 committed by GitHub
parent 0c6d83dc39
commit 198c447e77
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23

View file

@ -6,7 +6,9 @@ Certbot adheres to [Semantic Versioning](https://semver.org/).
### Added
*
* If possible, Certbot uses built-in support for OCSP from recent cryptography
versions instead of the OpenSSL binary: as a consequence Certbot does not need
the OpenSSL binary to be installed anymore if cryptography>=2.5 is installed.
### Changed
@ -49,9 +51,6 @@ More details about these changes can be found on our GitHub repo.
* Avoid reprocessing challenges that are already validated
when a certificate is issued.
* If possible, Certbot uses built-in support for OCSP from recent cryptography
versions instead of the OpenSSL binary: as a consequence Certbot does not need
the OpenSSL binary to be installed anymore if cryptography>=2.5 is installed.
* Support for initiating (but not solving end-to-end) TLS-ALPN-01 challenges
with the `acme` module.