--- a/OTP_VERSION +++ b/OTP_VERSION @@ -1 +1 @@ -18.3 +18.3.2 --- a/erts/doc/src/notes.xml +++ b/erts/doc/src/notes.xml @@ -32,6 +32,71 @@
This document describes the changes made to the ERTS application.
+
+
+ Own Id: OTP-13418
++ Make sure to create a crash dump when running out of + memory. This was accidentally removed in the erts-7.3 + release.
++ Own Id: OTP-13419
++ Schedulers could be woken by a premature timeout on + Linux. This premature wakeup was however harmless.
++ Own Id: OTP-13420
+
+ A process communicating with a port via one of the
+
+ This bug was introduced in erts version 5.10 (OTP R16A).
++ Own Id: OTP-13424 Aux Id: OTP-10336
++ The reference count of a process structure could under + rare circumstances be erroneously managed. When this + happened invalid memory accesses occurred.
++ Own Id: OTP-13446
+
+ Fix race between
+ A process could terminate due to exit signal even though
+
+ Own Id: OTP-13452
+The following data types are used in the functions for mod_esi:
+ +Currently supported key value pairs
+Indicates the inets version.
The local hostname.
Legacy string used in CGI, just ignore.
HTTP version, currently "HTTP/1.1"
Servers port number.
The clients ip address.
For TLS connections where client certificates are used this will
+ be an ASN.1 DER-encoded X509-certificate as an Erlang binary.
+ If client certificates are not used the value will be
Request URI
example: {http_content_type, "text/html"}
+ Add environment information item peer_cert to mod_esi
++ Own Id: OTP-13510
++ Mend ipv6_host_with_brackets option in httpc
++ Own Id: OTP-13417
++ Mnesia transactions could hang while waiting on a + response from a node who had stopped.
++ Own Id: OTP-13423
+This document describes the changes made to the SSL application.
++ Corrections to cipher suite handling using the 3 and 4 + tuple format in addition to commit + 89d7e21cf4ae988c57c8ef047bfe85127875c70c
++ Own Id: OTP-13511
++ Make values for the TLS-1.2 signature_algorithms + extension configurable
++ Own Id: OTP-13261
+Using
In addition to the algorithms negotiated by the cipher
+ suite used for key exchange, payload encryption, message
+ authentication and pseudo random calculation, the TLS signature
+ algorithm extension [
+%% SHA2
+{sha512, ecdsa},
+{sha512, rsa},
+{sha384, ecdsa},
+{sha384, rsa},
+{sha256, ecdsa},
+{sha256, rsa},
+{sha224, ecdsa},
+{sha224, rsa},
+%% SHA
+{sha, ecdsa},
+{sha, rsa},
+{sha, dsa},
+%% MD5
+{md5, rsa}
+]
+
+ The algorithms should be in the preferred order.
+ Selected signature algorithm can restrict which hash functions
+ that may be selected.
+
The algorithms specified by
+ this option will be the ones accepted by the server in a signature algorithm
+ negotiation, introduced in TLS-1.2. The algorithms will also be offered to the client if a
+ client certificate is requested. For more details see the