summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorNikos Mavrogiannopoulos <nmav@redhat.com>2016-12-01 10:04:45 +0100
committerNikos Mavrogiannopoulos <nmav@redhat.com>2016-12-01 10:04:45 +0100
commit563d7181247494a94d14d6116ccc98877b041b77 (patch)
treedcf965701fe4ca46214a0b50e9b9aca58e754011
parenteff5437cecbd4d329e91755c230d5a1666dd64ef (diff)
downloadgnutls-tmp-key-usage-fixes.tar.gz
-rw-r--r--NEWS15
1 files changed, 15 insertions, 0 deletions
diff --git a/NEWS b/NEWS
index c0e3694381..605235a247 100644
--- a/NEWS
+++ b/NEWS
@@ -20,6 +20,14 @@ See the end for copying conditions.
output the strict format by default, and can revert to the old one using
a flag.
+** libgnutls: [added missing news entry since 3.5.0]
+ No longer tolerate certificate key usage violations for
+ TLS signature verification, and decryption. That is GnuTLS will fail
+ to connect to servers which incorrectly use a restricted to signing certificate
+ for decryption, or vice-versa. This reverts the lax behavior introduced
+ in 3.1.0, due to several such broken servers being available. The %COMPAT
+ priority keyword can be used to work-around connecting on these servers.
+
** libgnutls: In all functions accepting UTF-8 passwords, ensure that
passwords are normalized according to RFC7613. When invalid UTF-8
passwords are detected, they are only tolerated for decryption.
@@ -340,6 +348,13 @@ gnutls_ext_get_name: Added
disable this protection by using the %GNUTLS_ALLOW_ID_CHANGE flag in
gnutls_init().
+** libgnutls: No longer tolerate certificate key usage violations for
+ TLS signature verification, and decryption. That is GnuTLS will fail
+ to connect to servers which incorrectly use a restricted to signing certificate
+ for decryption, or vice-versa. This reverts the lax behavior introduced
+ in 3.1.0, due to several such broken servers being available. The %COMPAT
+ priority keyword can be used to work-around connecting on these servers.
+
** libgnutls: Be strict in TLS extension decoding. That is, do not tolerate
parsing errors in the extensions field and treat it as a typical Hello
message structure. Reported by Hubert Kario (#40).