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 1/4] libxcrypt: Update to version 4.4.36
Date: Mon, 18 Sep 2023 16:16:54 +0200	[thread overview]
Message-ID: <20230918141810.536112-1-adolf.belka@ipfire.org> (raw)

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

- IPFire3.x
- Update from version 4.4.33 to 4.4.36
- Changelog
Version 4.4.36
	* Fix left over bits failing with Perl v5.38.0 (issue #173).
Version 4.4.35
	* Fix build with Perl v5.38.0 (issue #170).
	* Fix build with MinGW-w(32|64).
Version 4.4.34
	* Update build-aux/m4/ax_valgrind_check.m4 to v23.
	* Optimize some cast operation for performance in
	  lib/alg-yescrypt-platform.c.
	* Add SHA-2 Maj() optimization proposed by Wei Dai in lib/alg-sha512.c.
	* Explicitly clean the stack and context state after computation in
	  lib/alg-gost3411-2012-hmac.c, lib/alg-hmac-sha1.c, and lib/alg-sha256.c
	  (issue #168).

Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org>
---
 libxcrypt/libxcrypt.nm | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/libxcrypt/libxcrypt.nm b/libxcrypt/libxcrypt.nm
index 0005eba61..cd84935d9 100644
--- a/libxcrypt/libxcrypt.nm
+++ b/libxcrypt/libxcrypt.nm
@@ -4,8 +4,8 @@
 ###############################################################################
 
 name       = libxcrypt
-version    = 4.4.33
-release    = 2
+version    = 4.4.36
+release    = 1
 
 groups     = System/Libraries
 url        = https://github.com/besser82/libxcrypt/
-- 
2.42.0


             reply	other threads:[~2023-09-18 14:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-18 14:16 Adolf Belka [this message]
2023-09-18 14:16 ` [PATCH 2/4] apr: Include libxcrypt as dependency Adolf Belka
2023-09-18 14:16 ` [PATCH 3/4] apr-util: Update version to 1.6.3 and add " Adolf Belka
2023-09-18 14:16 ` [PATCH 4/4] apache: Introduce apache into IPFire3.x 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=20230918141810.536112-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