Message ID | 20221119175225.4019237-1-adolf.belka@ipfire.org |
---|---|
State | Accepted |
Commit | c81385f7f87b06fe6df6768a967eeaf7baa37e58 |
Headers |
Return-Path: <development-bounces@lists.ipfire.org> Received: from mail01.ipfire.org (mail01.haj.ipfire.org [172.28.1.202]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-384) client-signature ECDSA (P-384)) (Client CN "mail01.haj.ipfire.org", Issuer "R3" (verified OK)) by web04.haj.ipfire.org (Postfix) with ESMTPS id 4NF1St05vQz3wgd for <patchwork@web04.haj.ipfire.org>; Sat, 19 Nov 2022 17:52:30 +0000 (UTC) Received: from mail02.haj.ipfire.org (mail02.haj.ipfire.org [172.28.1.201]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-384) client-signature ECDSA (P-384)) (Client CN "mail02.haj.ipfire.org", Issuer "R3" (verified OK)) by mail01.ipfire.org (Postfix) with ESMTPS id 4NF1Ss317Vz1KB; Sat, 19 Nov 2022 17:52:29 +0000 (UTC) Received: from mail02.haj.ipfire.org (localhost [127.0.0.1]) by mail02.haj.ipfire.org (Postfix) with ESMTP id 4NF1Ss2sDlz2xk2; Sat, 19 Nov 2022 17:52:29 +0000 (UTC) Received: from mail01.ipfire.org (mail01.haj.ipfire.org [172.28.1.202]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-384) client-signature ECDSA (P-384)) (Client CN "mail01.haj.ipfire.org", Issuer "R3" (verified OK)) by mail02.haj.ipfire.org (Postfix) with ESMTPS id 4NF1Sq3nNhz2xJQ for <development@lists.ipfire.org>; Sat, 19 Nov 2022 17:52:27 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-384) server-digest SHA384) (No client certificate requested) by mail01.ipfire.org (Postfix) with ESMTPSA id 4NF1Sp67PNzdn; Sat, 19 Nov 2022 17:52:26 +0000 (UTC) DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003ed25519; t=1668880346; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version: content-transfer-encoding:content-transfer-encoding; bh=Ij1BJoG7LhNM/PggfBph6eAHfuGW+XqlJxNk9H6i/gc=; b=nTpA58RNhkevNiFS7xo9OE4ljmmHO77HlIARfTunLiPst2j02TkUMn6TjYjwbMP3/KncS0 QNiftb4bRT5sKaBg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa; t=1668880346; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version: content-transfer-encoding:content-transfer-encoding; bh=Ij1BJoG7LhNM/PggfBph6eAHfuGW+XqlJxNk9H6i/gc=; b=UfW0F3bBBcjf28LrVZNudAxxAwxbEQ9hVInT7RE6JgJdC0Ve4dz2h28Cy5pXdDdUYrfr/E zm2CIsgh7VmhEs1H1EEno8nKEznvAoaTOEXwVnc5aVu7Nw6skW//PHOO2/+CXceqb/wnOx 0vxek7QLoPf35bLicVu/tR7CrQyUxGW81onbKaINb/DJZMFDZksN1phzn1awjX5QF1Cz1Y W2CJEagQiuKDx5n0z6GvPWSw7SvI1bbhSct+vNC+dfYPoW6ZXkfPoS1+7c6L4Uz3XvSjG/ daggHWwXsZlc00R5WmjLmVHY3KBndBVwv4HUrB/Eyz37yVMo4dVP+GdPQYdd1w== From: Adolf Belka <adolf.belka@ipfire.org> To: development@lists.ipfire.org Subject: [PATCH] libxcrypt: Update to version 4.4.33 Date: Sat, 19 Nov 2022 18:52:25 +0100 Message-Id: <20221119175225.4019237-1-adolf.belka@ipfire.org> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: development@lists.ipfire.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: IPFire development talk <development.lists.ipfire.org> List-Unsubscribe: <https://lists.ipfire.org/mailman/options/development>, <mailto:development-request@lists.ipfire.org?subject=unsubscribe> List-Archive: <http://lists.ipfire.org/pipermail/development/> List-Post: <mailto:development@lists.ipfire.org> List-Help: <mailto:development-request@lists.ipfire.org?subject=help> List-Subscribe: <https://lists.ipfire.org/mailman/listinfo/development>, <mailto:development-request@lists.ipfire.org?subject=subscribe> Errors-To: development-bounces@lists.ipfire.org Sender: "Development" <development-bounces@lists.ipfire.org> |
Series |
libxcrypt: Update to version 4.4.33
|
|
Commit Message
Adolf Belka
Nov. 19, 2022, 5:52 p.m. UTC
- Update from version 4.4.28 to 4.4.33
- Update of rootfile not required
- Changelog
Version 4.4.33
* Fix -Werror=sign-conversion in lib/alg-yescrypt-platform.c.
With commit 894aee75433b4dc8d9724b126da6e79fa5f6814b we introduced some
changes to huge page handling, that show this error when building with
GCC v12.2.1, and thus need a small fix.
Version 4.4.32
* Improvements to huge page handling in lib/alg-yescrypt-platform.c.
When explicitly using huge pages, request the 2 MiB page size.
This should fix the issue where on a system configured to use 1 GiB
huge pages we'd fail on munmap() as we're only rounding the size up
to a multiple of 2 MiB. With the fix, we wouldn't use huge pages on
such a system. Unfortunately, now we also wouldn't use huge pages on
Linux kernels too old to have MAP_HUGE_2MB (issue #152).
Version 4.4.31
* Fix -Werror=conversion in lib/alg-yescrypt-opt.c
(issues #161 and #162).
* Add some SHA-2 Maj() optimization in lib/alg-sha256.c.
* Fix issues found by Covscan in test/getrandom-fallback.c.
* Fix -Werror=strict-overflow in lib/crypt-des.c, which is seen
by GCC 12.x (issues #155 and #163).
Version 4.4.30
* configure: Restore ucontext api functionality check.
In c3f01c72b303cbbb0cc8983120677edee2f3fa4b the use of the ucontext api
in the main program was removed, and with it the configure check for it.
However, the ucontext api is still used in the "explicit_bzero" test and
thus this test still needs to be in place.
See also: https://bugs.gentoo.org/838172
* configure: Restore the functionality of the '--disable-symvers' switch.
Without this fix the build was simply broken, if symbol versioning was
disabled for any reason, e.g. whether the compiler nor the linker
supporting it, or if disabled on purpose by the user (issue #142).
* Fix variable name in crypt(3) for a datamember of 'struct crypt_data'
(issue #153).
Version 4.4.29
* Add glibc-on-loongarch-lp64 (Loongson LA464 / LA664) entry to
libcrypt.minver. This was added in GNU libc 2.36.
Signed-off-by: Adolf Belka <adolf.belka@ipfire.org>
---
lfs/libxcrypt | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
Comments
Reviewed-by: Michael Tremer <michael.tremer@ipfire.org> > On 19 Nov 2022, at 17:52, Adolf Belka <adolf.belka@ipfire.org> wrote: > > - Update from version 4.4.28 to 4.4.33 > - Update of rootfile not required > - Changelog > Version 4.4.33 > * Fix -Werror=sign-conversion in lib/alg-yescrypt-platform.c. > With commit 894aee75433b4dc8d9724b126da6e79fa5f6814b we introduced some > changes to huge page handling, that show this error when building with > GCC v12.2.1, and thus need a small fix. > Version 4.4.32 > * Improvements to huge page handling in lib/alg-yescrypt-platform.c. > When explicitly using huge pages, request the 2 MiB page size. > This should fix the issue where on a system configured to use 1 GiB > huge pages we'd fail on munmap() as we're only rounding the size up > to a multiple of 2 MiB. With the fix, we wouldn't use huge pages on > such a system. Unfortunately, now we also wouldn't use huge pages on > Linux kernels too old to have MAP_HUGE_2MB (issue #152). > Version 4.4.31 > * Fix -Werror=conversion in lib/alg-yescrypt-opt.c > (issues #161 and #162). > * Add some SHA-2 Maj() optimization in lib/alg-sha256.c. > * Fix issues found by Covscan in test/getrandom-fallback.c. > * Fix -Werror=strict-overflow in lib/crypt-des.c, which is seen > by GCC 12.x (issues #155 and #163). > Version 4.4.30 > * configure: Restore ucontext api functionality check. > In c3f01c72b303cbbb0cc8983120677edee2f3fa4b the use of the ucontext api > in the main program was removed, and with it the configure check for it. > However, the ucontext api is still used in the "explicit_bzero" test and > thus this test still needs to be in place. > See also: https://bugs.gentoo.org/838172 > * configure: Restore the functionality of the '--disable-symvers' switch. > Without this fix the build was simply broken, if symbol versioning was > disabled for any reason, e.g. whether the compiler nor the linker > supporting it, or if disabled on purpose by the user (issue #142). > * Fix variable name in crypt(3) for a datamember of 'struct crypt_data' > (issue #153). > Version 4.4.29 > * Add glibc-on-loongarch-lp64 (Loongson LA464 / LA664) entry to > libcrypt.minver. This was added in GNU libc 2.36. > > Signed-off-by: Adolf Belka <adolf.belka@ipfire.org> > --- > lfs/libxcrypt | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > diff --git a/lfs/libxcrypt b/lfs/libxcrypt > index 56a27f33e..bdb6818eb 100644 > --- a/lfs/libxcrypt > +++ b/lfs/libxcrypt > @@ -24,7 +24,7 @@ > > include Config > > -VER = 4.4.28 > +VER = 4.4.33 > > THISAPP = libxcrypt-$(VER) > DL_FILE = $(THISAPP).tar.xz > @@ -47,7 +47,7 @@ objects = $(DL_FILE) > > $(DL_FILE) = $(DL_FROM)/$(DL_FILE) > > -$(DL_FILE)_BLAKE2 = cf40994c461bb0161b1fd585cbc3881d98cbe3d494cfaa33f89c4e1cedcd593f5b603b58309dadbaa7cd436bfabe74b0d2d9a8fafd3a2212f5ef5b18e6f67161 > +$(DL_FILE)_BLAKE2 = 9cd2a2df4e2399d9084a5e03cb9be45e70c0213e1f143d423b5043f8f331320c79e6b8efa7ff33d401bce41a32574c6d6866096b70bf14ed715416c638f43a21 > > install : $(TARGET) > > -- > 2.38.1 >
diff --git a/lfs/libxcrypt b/lfs/libxcrypt index 56a27f33e..bdb6818eb 100644 --- a/lfs/libxcrypt +++ b/lfs/libxcrypt @@ -24,7 +24,7 @@ include Config -VER = 4.4.28 +VER = 4.4.33 THISAPP = libxcrypt-$(VER) DL_FILE = $(THISAPP).tar.xz @@ -47,7 +47,7 @@ objects = $(DL_FILE) $(DL_FILE) = $(DL_FROM)/$(DL_FILE) -$(DL_FILE)_BLAKE2 = cf40994c461bb0161b1fd585cbc3881d98cbe3d494cfaa33f89c4e1cedcd593f5b603b58309dadbaa7cd436bfabe74b0d2d9a8fafd3a2212f5ef5b18e6f67161 +$(DL_FILE)_BLAKE2 = 9cd2a2df4e2399d9084a5e03cb9be45e70c0213e1f143d423b5043f8f331320c79e6b8efa7ff33d401bce41a32574c6d6866096b70bf14ed715416c638f43a21 install : $(TARGET)