From: Pieter Wuille <bitcoin-dev@wuille.net>
To: Bitcoin dev list <bitcoin-dev@lists.linuxfoundation.org>
Subject: [bitcoin-dev] libsecp256k1 v0.3.1 released
Date: Mon, 10 Apr 2023 20:00:29 +0000 [thread overview]
Message-ID: <pD2ktCvYbpX4xW6Cp_UWpf6elaJXjLvbJ0BuEVyx7bcywkNG2wJ-jnFrEvi3WPVYZsvInX4kp19NymrKRoqFORonFh-64NdGClZKg8ia4l0=@wuille.net> (raw)
Hello,
Today we'd like to announce the release of version 0.3.1 of libsecp256k1:
https://github.com/bitcoin-core/secp256k1/releases/tag/v0.3.1
This is a bugfix release after 0.3.0 (which was not announced on this list). For the full release notes of 0.3.0 and 0.3.1 see:
https://github.com/bitcoin-core/secp256k1/blob/master/CHANGELOG.md
but the impetus for this release is the discovery that Clang 14 and later became smart enough to optimize out a specific timing side-channel protection mechanism in the code that could leave applications vulnerable to a side-channel attack. This has been fixed in 0.3.1.
We strongly recommend any users of the library to upgrade if their code may end up being compiled with Clang 14+. Bitcoin Core release binaries are not affected.
--
Pieter
reply other threads:[~2023-04-10 20:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='pD2ktCvYbpX4xW6Cp_UWpf6elaJXjLvbJ0BuEVyx7bcywkNG2wJ-jnFrEvi3WPVYZsvInX4kp19NymrKRoqFORonFh-64NdGClZKg8ia4l0=@wuille.net' \
--to=bitcoin-dev@wuille.net \
--cc=bitcoin-dev@lists.linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox