summaryrefslogtreecommitdiff
path: root/doc/rst/legacy/nss_releases/nss_3.31_release_notes/index.rst
diff options
context:
space:
mode:
Diffstat (limited to 'doc/rst/legacy/nss_releases/nss_3.31_release_notes/index.rst')
-rw-r--r--doc/rst/legacy/nss_releases/nss_3.31_release_notes/index.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/rst/legacy/nss_releases/nss_3.31_release_notes/index.rst b/doc/rst/legacy/nss_releases/nss_3.31_release_notes/index.rst
index 2c80c618b..3caa79b5c 100644
--- a/doc/rst/legacy/nss_releases/nss_3.31_release_notes/index.rst
+++ b/doc/rst/legacy/nss_releases/nss_3.31_release_notes/index.rst
@@ -89,11 +89,11 @@ NSS 3.31 release notes
overlap with a systemwide crypto policy, if configured. **SSL_VersionRangeGetSupported** can
be used to query the overlap between the library's supported range of TLS versions and the
systemwide policy.
- - Previously, **SSL_VersionRangeSet** and **SSL_VersionRangeSetDefault** returned a failure if
+ - Previously, **SSL_VersionRangeSet** and **SSL_VersionRangeSetDefault** returned a failure if
the requested version range wasn't fully allowed by the systemwide crypto policy. They have
been changed to return success, if at least one TLS version overlaps between the requested
range and the systemwide policy. An application may call **SSL_VersionRangeGet**
- and **SSL_VersionRangeGetDefault** to query the TLS version range that was effectively
+ and **SSL_VersionRangeGetDefault** to query the TLS version range that was effectively
activated.
- Corrected the encoding of Domain Name Constraints extensions created by certutil
- NSS supports a clean seeding mechanism for \*NIX systems now using only /dev/urandom. This is