package/libgcrypt: bump version to 1.2.3
PATCH 1/1 package/libgcrypt: bump version to 1.2.3
Release notes:
https://lists.gnu.org/archive/html/info-gnu/2026-08/msg00007.html
Contains a number of bugfixes, some of which may have (low severity) security impact. As stated by Werner Koch:
All in all we received 26 reports alone from ANSSI but as even the reporter mentioned, the real world attack severity is not critical. Thus we don't consider 1.12.3 a security fix release. There are some bugs which should be fixed to avoid crashes, and thus may lead to DoS. However, 16384 bit RSA keys can also be used for a practical DoS; it all depends on your use case.
https://www.openwall.com/lists/oss-security/2026/08/31/11
--- package/libgcrypt/libgcrypt.hash | 4 ++-- package/libgcrypt/libgcrypt.mk | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-)
package/libgcrypt/libgcrypt.hash +2 -2
@@ -1,5 +1,5 @@ # From https://www.gnupg.org/download/integrity_check.html -sha1 7b8ff21966a0b6e7a735466b9b9b55d9dac9fa87 libgcrypt-1.12.2.tar.bz2 -sha256 7ce33c2492221a0436f96a8500215e9f3e3dcb5fd26a757cd415e7a843babd5e libgcrypt-1.12.2.tar.bz2 +sha1 b4654d75f0e5d0850cc699f02c9b44a06367502f libgcrypt-1.12.3.tar.bz2 +sha256 98d1b0b3202d2b03fa754a35aa3cbbfcf526a3260d8d2ee213748001b1043006 libgcrypt-1.12.3.tar.bz2 # Locally calculated sha256 20e50fe7aae3e56378ebf0417d9de904f55a0e61e4df315333e632a4d3555d95 COPYING.LIB
package/libgcrypt/libgcrypt.mk +1 -1
@@ -4,7 +4,7 @@ # ################################################################################ -LIBGCRYPT_VERSION = 1.12.2 +LIBGCRYPT_VERSION = 1.12.3 LIBGCRYPT_SOURCE = libgcrypt-$(LIBGCRYPT_VERSION).tar.bz2 LIBGCRYPT_LICENSE = LGPL-2.1+ LIBGCRYPT_LICENSE_FILES = COPYING.LIB
Signature · 6 lines
2.47.3 _______________________________________________ buildroot mailing list [email protected] https://lists.buildroot.org/mailman/listinfo/buildroot
Hi Peter,
The commit title says "1.2.3" but should rather be "1.12.3".
Quoted 22 lines · Peter Korsgaard
Release notes:
https://lists.gnu.org/archive/html/info-gnu/2026-08/msg00007.htmlContains a number of bugfixes, some of which may have (low severity) security impact. As stated by Werner Koch:
All in all we received 26 reports alone from ANSSI but as even the
reporter
mentioned, the real world attack severity is not critical. Thus we
don't
consider 1.12.3 a security fix release. There are some bugs which
should
be fixed to avoid crashes, and thus may lead to DoS. However, 16384
bit
RSA keys can also be used for a practical DoS; it all depends on your
use
case.https://www.openwall.com/lists/oss-security/2026/08/31/11
Signed-off-by Peter Korsgaard <[email protected]>---
[...]
package/libgcrypt/libgcrypt.mk line 8
Quoted 11 lines
package/libgcrypt/libgcrypt.mk +1
-1@@ -4,7 +4,7 @@ # ################################################################################ -LIBGCRYPT_VERSION = 1.12.2 +LIBGCRYPT_VERSION = 1.12.3
Also, this new version introduces build failures:
https://gitlab.com/jolivain/buildroot/-/pipelines/2810830147
For reference, the previous version 1.12.2 passes test-pkg:
https://gitlab.com/jolivain/buildroot/-/pipelines/2810888453
Since those fixes are described as low severity, we should probably fix those before merging this bump.
Quoted 5 lines
package/libgcrypt/libgcrypt.mk +0
-0LIBGCRYPT_SOURCE = libgcrypt-$(LIBGCRYPT_VERSION).tar.bz2 LIBGCRYPT_LICENSE = LGPL-2.1+
LIBGCRYPT_LICENSE_FILES= COPYING.LIB
--
2.47.3
Best regards,
Julien.
_______________________________________________
buildroot mailing list
[email protected]
https://lists.buildroot.org/mailman/listinfo/buildroot
Quoted 4 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
"Julien" == Julien Olivain <[email protected]> writes:
Hi Peter,
The commit title says "1.2.3" but should rather be "1.12.3".
Ups, indeed ;)
Quoted 34 lines · Peter Korsgaard
Quoted 18 lines
Release notes:
https://lists.gnu.org/archive/html/info-gnu/2026-08/msg00007.html
Contains a number of bugfixes, some of which may have (low severity) security impact. As stated by Werner Koch:
All in all we received 26 reports alone from ANSSI but as even the reporter
mentioned, the real world attack severity is not critical. Thus we don't
consider 1.12.3 a security fix release. There are some bugs which should
be fixed to avoid crashes, and thus may lead to DoS. However, 16384 bit
RSA keys can also be used for a practical DoS; it all depends on your use
case.
https://www.openwall.com/lists/oss-security/2026/08/31/11Signed-off-by Peter Korsgaard <[email protected]>---
[...]
package/libgcrypt/libgcrypt.mk line 6
Quoted 10 lines
package/libgcrypt/libgcrypt.mk +1
-1@@ -4,7 +4,7 @@ # ################################################################################ -LIBGCRYPT_VERSION = 1.12.2 +LIBGCRYPT_VERSION = 1.12.3Also, this new version introduces build failures:
https://gitlab.com/jolivain/buildroot/-/pipelines/2810830147
Quoted 5 lines
For reference, the previous version 1.12.2 passes test-pkg:
https://gitlab.com/jolivain/buildroot/-/pipelines/2810888453Since those fixes are described as low severity, we should probably fix those before merging this bump.
Yes, I will take a look - Thanks.
Signature · 5 lines
Bye, Peter Korsgaard _______________________________________________ buildroot mailing list [email protected] https://lists.buildroot.org/mailman/listinfo/buildroot