The OPENSSL_s390xcap environment variable can be used to set bits in the S390X capability vector to zero.
TLS_MAX_VERSION, DTLS_MAX_VERSION and DTLS_MIN_VERSION constants are now deprecated. Make OSSL_PARAM_BLD_push_BN() return an error on negative numbers.Īllow copying uninitialized digest contexts with EVP_MD_CTX_copy_ex.įixed detection of ARMv7 and ARM64 CPU features on FreeBSD.Īdded NULL digest implementation to keep compatibility with 1.1.1 version.Īllow fetching an operation from the provider that owns an unexportable key as a fallback if that is still allowed by the property query. Multiple fixes in the OSSL_HTTP API functions.Īllow sign extension in OSSL_PARAM_allocate_from_text() for the OSSL_PARAM_INTEGER data type and return error on negative numbers used with the OSSL_PARAM_UNSIGNED_INTEGER data type.
Backwards compatible apache air assault verification#
Slightly enhanced the installation verification script.įixed EVP_PKEY_eq() to make it possible to use it with strictly private keys.įixed PVK encoder to properly query for the passphrase. ()Ĭorrected a few file name and file reference bugs in the build, installation and setup scripts, which lead to installation verification failures. This issue can occur even with valid chains. This will occur where a certificate does not include the Subject Alternative Name extension but where a Certificate Authority has enforced name constraints. This issue is made more serious in combination with a separate bug in OpenSSL 3.0 that will cause X509_verify_cert() to indicate an internal error when processing a certificate chain. The exact behaviour will depend on the application but it could result in crashes, infinite loops or other similar incorrect responses. Since most applications do not do this the SSL_ERROR_WANT_RETRY_VERIFY return value from SSL_get_error() will be totally unexpected and applications may not behave correctly as a result. This return value is only supposed to be returned by OpenSSL if the application has previously called SSL_CTX_set_cert_verify_callback(). Such a negative return value is mishandled by OpenSSL and will cause an IO function (such as SSL_connect() or SSL_do_handshake()) to not indicate success and a subsequent call to SSL_get_error() to return the value SSL_ERROR_WANT_RETRY_VERIFY. That function may return a negative return value to indicate an internal error (for example out of memory). Changes between 3.0.0 and 3.0.1 įixed invalid handling of X509_verify_cert() internal errors in libssl Internally libssl in OpenSSL calls X509_verify_cert() on the client side to verify a certificate supplied by a server. The migration guide contains more detailed information related to new features, breaking changes, and mappings for the large list of deprecated functions. Sergey Kirillov, Andrey Matyukov (Intel Corp)įor OpenSSL 3.0 a Migration guide has been added, so the CHANGES entries listed here are only a brief description. Parallel dual-prime 1536/2048-bit modular exponentiation for AVX512_IFMA capable processors. Subject or issuer names in X.509 objects are now displayed as UTF-8 strings by default. The various OBJ_* functions have been made thread safe.ĬCM8 cipher suites in TLS have been downgraded to security level zero because they use a short authentication tag which lowers their strength. Applications requiring this KDF will need to load the legacy crypto provider. The PVK key derivation function has been moved from b2i_PVK_bio_ex() into the legacy crypto provider as an EVP_KDF. The SSL_CTX_set_cipher_list family functions now accept ciphers using their IANA standard names. At security level 2 it cannot be enabled. By default TLS compression was already disabled in previous OpenSSL versions. RSA, DSA and DH keys of 1024 bits and above and less than 2048 bits and ECC keys of 160 bits and above and less than 224 bits were previously accepted by default but are now no longer allowed. The default SSL/TLS security level has been changed from 1 to 2. This avoids confusion between that scenario versus when the TLS version includes secure renegotiation but the peer lacks support for it. S_client and s_server apps now explicitly say when the TLS version does not include the renegotiation mechanism. RNDR and RNDRRS support in provider functions to provide random number generation for Arm CPUs (aarch64). The plain-text / markdown version of this document is availableįor other branches, the changelogs are distributed with This is the changelog for the master branch, the one that is Any changes thatĪre merged across branches, however, should have an entry For example, none of the changesĪfter 0.9.8n appear in the other logs, because 1.0.0 wasĬreated after that release and before 0.9.8o. When a release is created, that branch is forked off, and itsĬhangelog is also forked.
0 kommentar(er)
