public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
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	[thread overview]
Message-ID: <20221119175225.4019237-1-adolf.belka@ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 2987 bytes --]

- 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(a)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


             reply	other threads:[~2022-11-19 17:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-19 17:52 Adolf Belka [this message]
2022-11-21  9:45 ` Michael Tremer

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=20221119175225.4019237-1-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