# OTP 25.1 Released **URL:** \ **Category:** Erlang News\ **Tags:** erlang-release\ **Created:** [September 21, 2022, 1:04pm UTC](https://erlangforums.com/t/otp-25-1-released/1854 "2022-09-21T13:04:58Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![proxyles](https://erlangforums.com/letter_avatar_proxy/v4/letter/p/9de053/32.png) [@proxyles](https://erlangforums.com/u/proxyles)\ **Post date:** [September 21, 2022, 1:04pm UTC](https://erlangforums.com/t/otp-25-1-released/1854/1 "2022-09-21T13:04:58Z")
## OTP 25.1 Erlang/OTP 25.1 is the first maintenance patch package for OTP 25, with mostly bug fixes as well as quite many small improvements. Below are some highlights of the release: ### crypto: - Crypto is now considered to be usable with the OpenSSL 3.0 cryptolib for production code. ENGINE and FIPS are not yet fully functional. - Changed the behaviour of the engine load/unload functions ### ssl: - A vulnerability has been discovered and corrected. It is registered as CVE-2022-37026 “Client Authentication Bypass”. Corrections have been released on the supported tracks with patches 23.3.4.15, 24.3.4.2, and 25.0.2. The vulnerability might also exist in older OTP versions. We recommend that impacted users upgrade to one of these versions or later on the respective tracks. OTP 25.1 would be an even better choice. Impacted are those who are running an `ssl/tls/dtls` server using the `ssl` application either directly or indirectly via other applications. For example via `inets` (`httpd`), `cowboy`, etc. Note that the vulnerability only affects servers that request client certification, that is sets the option `{verify, verify_peer}`. [For more details and downloads follow this link](https://erlang.org/patches/OTP-25.1) The Erlang/OTP source can also be found at GitHub on the official Erlang repository, > **[GitHub - erlang/otp: Erlang/OTP](https://github.com/erlang/otp)** > > Erlang/OTP ---
**Author:** ![proxyles](https://erlangforums.com/letter_avatar_proxy/v4/letter/p/9de053/32.png) [@proxyles](https://erlangforums.com/u/proxyles)\ **Post date:** [September 21, 2022, 1:06pm UTC](https://erlangforums.com/t/otp-25-1-released/1854/2 "2022-09-21T13:06:53Z")
---
**Author:** ![NelsonVides](https://erlangforums.com/user_avatar/erlangforums.com/nelsonvides/32/1205_2.png) [@NelsonVides](https://erlangforums.com/u/NelsonVides)\ **Post date:** [September 23, 2022, 4:37pm UTC](https://erlangforums.com/t/otp-25-1-released/1854/3 "2022-09-23T16:37:46Z")
After upgrading to this release, `rebar3 eunit` is failing after the `exact_execution` is not in the options list, in here [otp/eunit\_data.erl at c194380712236c301188f0b401352f14c608c145 · u3s/otp · GitHub](https://github.com/u3s/otp/blob/c194380712236c301188f0b401352f14c608c145/lib/eunit/src/eunit_data.erl#L581) 😢 * * * To be precise, the error is that options is an empty list! So all `proplists:X/2` will fail with a `function_clause` error when executed. ---
**Author:** ![mikpe](https://erlangforums.com/letter_avatar_proxy/v4/letter/m/b487fb/32.png) [@mikpe](https://erlangforums.com/u/mikpe)\ **Post date:** [September 23, 2022, 8:12pm UTC](https://erlangforums.com/t/otp-25-1-released/1854/4 "2022-09-23T20:12:59Z")
Check the Erlang/OTP github repo, both open issues and pull requests. There are multiple reports about rebar3 eunit failing with OTP-25.1. In particular see [eunit: Fix `$ rebar3 eunit` error on OTP 25.1 by sile · Pull Request #6322 · erlang/otp · GitHub](https://github.com/erlang/otp/pull/6322) . I would recommend people to stay on 25.0.4 until a patch release (likely 25.1.1 but who knows) fixes the issue. ---
**Author:** ![kuba](https://erlangforums.com/user_avatar/erlangforums.com/kuba/32/194_2.png) [@kuba](https://erlangforums.com/u/kuba)\ **Post date:** [September 27, 2022, 12:30pm UTC](https://erlangforums.com/t/otp-25-1-released/1854/5 "2022-09-27T12:30:27Z")
Eunit fix is planned to be released with OTP25.1.1 this week. ---
**Author:** ![kuba](https://erlangforums.com/user_avatar/erlangforums.com/kuba/32/194_2.png) [@kuba](https://erlangforums.com/u/kuba)\ **Post date:** [September 30, 2022, 10:52am UTC](https://erlangforums.com/t/otp-25-1-released/1854/6 "2022-09-30T10:52:46Z")
25.1.1 will be delayed till Monday, sorry for inconvenience. ---
**Author:** ![abhilash.vankayala](https://erlangforums.com/user_avatar/erlangforums.com/abhilash.vankayala/32/1896_2.png) [@abhilash.vankayala](https://erlangforums.com/u/abhilash.vankayala)\ **Post date:** [November 22, 2022, 6:06pm UTC](https://erlangforums.com/t/otp-25-1-released/1854/7 "2022-11-22T18:06:00Z")
Currently we are using Erlang 25.1.2 Version for the purpose of RabbitMQ and we have a security Vulnerability identified as part of Erlang otp installation, which indicates Erlang 25.1.2 using Crypto.dll (5.2.1) which using a vulnerable Openssl 1.1.1q. Is this vulnerable valid and is crypto.dll using OpenSll.1.1.1q or some other latest version? ---
**Author:** ![ingela](https://erlangforums.com/letter_avatar_proxy/v4/letter/i/53a042/32.png) [@ingela](https://erlangforums.com/u/ingela)\ **Post date:** [November 23, 2022, 8:14am UTC](https://erlangforums.com/t/otp-25-1-released/1854/8 "2022-11-23T08:14:09Z")
OTP-25.1.2 does not depend on a special version of OpenSSL that depends on your build. If the vulnerability is for OpenSSL protocol implementation it is not relevant for OTP only if the vulnerability is on the libcrypto functions will it also affect OTP. ---
**Author:** ![AstonJ](https://erlangforums.com/user_avatar/erlangforums.com/astonj/32/9_2.png) [@AstonJ](https://erlangforums.com/u/AstonJ)\ **Post date:** [January 7, 2023, 9:20pm UTC](https://erlangforums.com/t/otp-25-1-released/1854/9 "2023-01-07T21:20:22Z")
A post was split to a new topic: [Noticed that compiling OTP with kerl or from the source binaries (elf files) are built with the debug info - is that intentional?](https://erlangforums.com/t/noticed-that-compiling-otp-with-kerl-or-from-the-source-binaries-elf-files-are-built-with-the-debug-info-is-that-intentional/2243) ---
**Author:** ![AstonJ](https://erlangforums.com/user_avatar/erlangforums.com/astonj/32/9_2.png) [@AstonJ](https://erlangforums.com/u/AstonJ)\ **Post date:** [March 13, 2023, 3:21pm UTC](https://erlangforums.com/t/otp-25-1-released/1854/11 "2023-03-13T15:21:34Z")
A post was split to a new topic: [Will Erlang/OTP 25+ has plan to fully support FIPS?](https://erlangforums.com/t/will-erlang-otp-25-has-plan-to-fully-support-fips/2450)