Add a CHANGES entry for the unrecognised record type change
Reviewed-by: Tim Hudson <tjh@openssl.org>
This commit is contained in:
parent
1f3e70a450
commit
ce95f3b724
1 changed files with 5 additions and 1 deletions
6
CHANGES
6
CHANGES
|
@ -4,7 +4,11 @@
|
||||||
|
|
||||||
Changes between 1.1.0a and 1.1.1 [xx XXX xxxx]
|
Changes between 1.1.0a and 1.1.1 [xx XXX xxxx]
|
||||||
|
|
||||||
*)
|
*) OpenSSL now fails if it receives an unrecognised record type in TLS1.0
|
||||||
|
or TLS1.1. Previously this only happened in SSLv3 and TLS1.2. This is to
|
||||||
|
prevent issues where no progress is being made and the peer continually
|
||||||
|
sends unrecognised record types, using up resources processing them.
|
||||||
|
[Matt Caswell]
|
||||||
|
|
||||||
*) 'openssl passwd' can now produce SHA256 and SHA512 based output,
|
*) 'openssl passwd' can now produce SHA256 and SHA512 based output,
|
||||||
using the algorithm defined in
|
using the algorithm defined in
|
||||||
|
|
Loading…
Reference in a new issue