You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/secp256k1/CHANGELOG.md
+21-1Lines changed: 21 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,6 +7,25 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
7
7
8
8
## [Unreleased]
9
9
10
+
## [0.3.2] - 2023-05-13
11
+
We strongly recommend updating to 0.3.2 if you use or plan to use GCC >=13 to compile libsecp256k1. When in doubt, check the GCC version using `gcc -v`.
12
+
13
+
#### Security
14
+
- Module `ecdh`: Fix "constant-timeness" issue with GCC 13.1 (and potentially future versions of GCC) that could leave applications using libsecp256k1's ECDH module vulnerable to a timing side-channel attack. The fix avoids secret-dependent control flow during ECDH computations when libsecp256k1 is compiled with GCC 13.1.
15
+
16
+
#### Fixed
17
+
- Fixed an old bug that permitted compilers to potentially output bad assembly code on x86_64. In theory, it could lead to a crash or a read of unrelated memory, but this has never been observed on any compilers so far.
18
+
19
+
#### Changed
20
+
- Various improvements and changes to CMake builds. CMake builds remain experimental.
21
+
- Made API versioning consistent with GNU Autotools builds.
22
+
- Switched to `BUILD_SHARED_LIBS` variable for controlling whether to build a static or a shared library.
23
+
- Added `SECP256K1_INSTALL` variable for the controlling whether to install the build artefacts.
24
+
- Renamed asm build option `arm` to `arm32`. Use `--with-asm=arm32` instead of `--with-asm=arm` (GNU Autotools), and `-DSECP256K1_ASM=arm32` instead of `-DSECP256K1_ASM=arm` (CMake).
25
+
26
+
#### ABI Compatibility
27
+
The ABI is compatible with versions 0.3.0 and 0.3.1.
28
+
10
29
## [0.3.1] - 2023-04-10
11
30
We strongly recommend updating to 0.3.1 if you use or plan to use Clang >=14 to compile libsecp256k1, e.g., Xcode >=14 on macOS has Clang >=14. When in doubt, check the Clang version using `clang -v`.
12
31
@@ -68,7 +87,8 @@ This version was in fact never released.
68
87
The number was given by the build system since the introduction of autotools in Jan 2014 (ea0fe5a5bf0c04f9cc955b2966b614f5f378c6f6).
69
88
Therefore, this version number does not uniquely identify a set of source files.
0 commit comments