public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Cc: Adolf Belka <adolf.belka@ipfire.org>
Subject: [PATCH] libgcrypt: Update to version 1.12.4
Date: Sun, 20 Sep 2026 14:51:13 +0200	[thread overview]
Message-ID: <20260920125116.3492275-3-adolf.belka@ipfire.org> (raw)
In-Reply-To: <20260920125116.3492275-1-adolf.belka@ipfire.org>

- Update from version 1.12.3 to 1.12.4
- Update of rootfile
- Changelog
1.12.4
 * Bug fixes:
   * Fix build problem with some compiler versions related to SM4
     instructions.  [rCf0bc379e0f]
   * Fix padding in cSHAKE found by NIST ACVP conformance vectors.
     [rCf54ce47180]
   * Fix RSA PSS handling of huge salt lengths.  [T8377]
   * Validate the length of hashed input for RSA PSS.  [T8391]
   * Improve RSA OAEP decoder correctnes by validating an all-zero
     padding.  [T8390]

Signed-off-by: Adolf Belka <adolf.belka@ipfire.org>
---
 config/rootfiles/common/libgcrypt | 2 +-
 lfs/libgcrypt                     | 4 ++--
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/config/rootfiles/common/libgcrypt b/config/rootfiles/common/libgcrypt
index 1825a29bf..01ff197b8 100644
--- a/config/rootfiles/common/libgcrypt
+++ b/config/rootfiles/common/libgcrypt
@@ -5,7 +5,7 @@
 #usr/lib/libgcrypt.la
 #usr/lib/libgcrypt.so
 usr/lib/libgcrypt.so.20
-usr/lib/libgcrypt.so.20.8.8
+usr/lib/libgcrypt.so.20.8.9
 #usr/lib/pkgconfig/libgcrypt.pc
 #usr/share/aclocal/libgcrypt.m4
 #usr/share/info/gcrypt.info
diff --git a/lfs/libgcrypt b/lfs/libgcrypt
index f574c63db..074e338e4 100644
--- a/lfs/libgcrypt
+++ b/lfs/libgcrypt
@@ -24,7 +24,7 @@
 
 include Config
 
-VER        = 1.12.3
+VER        = 1.12.4
 
 THISAPP    = libgcrypt-$(VER)
 DL_FILE    = $(THISAPP).tar.bz2
@@ -40,7 +40,7 @@ objects = $(DL_FILE)
 
 $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
 
-$(DL_FILE)_BLAKE2 = 52043c1defdbaf3ed0618bfbac13f4186dd28a4b2507a93bc24f08a7b2e66bb77014ff875801a3e39fcfbc905224f6ff1bcee43dcd53c555c32940305cfa92fe
+$(DL_FILE)_BLAKE2 = c30aed945b7050c38094258f5d4cad480e9b1fdf018378f07058542e129275d7be41cc7b512cda474d96c12c9920e0256e89242b2c2ee5dd4243e1f4bd178cb9
 
 install : $(TARGET)
 
-- 
2.55.0



  parent reply	other threads:[~2026-09-20 12:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-20 12:51 [PATCH] core205: Ship libtirpc Adolf Belka
2026-09-20 12:51 ` [PATCH] core205: Ship openldap Adolf Belka
2026-09-20 12:51 ` Adolf Belka [this message]
2026-09-20 12:51 ` [PATCH] libpcap: Update to version 1.11.0 Adolf Belka
2026-09-20 12:51 ` [PATCH] libtirpc: Update to version 1.3.8 Adolf Belka
2026-09-20 12:51 ` [PATCH] openldap: Update to version 2.7.1 Adolf Belka

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=20260920125116.3492275-3-adolf.belka@ipfire.org \
    --to=adolf.belka@ipfire.org \
    --cc=development@lists.ipfire.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