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.28
Date: Wed, 09 Feb 2022 22:29:27 +0100	[thread overview]
Message-ID: <20220209212927.2754152-1-adolf.belka@ipfire.org> (raw)

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

- Update from 4.4.26.to 4.4.28
- Update of rootfile not required
- Changelog - This is from the NEWS file in the source tarball. Since version 3.1.1 there
   is no Changelog provided, only the NEWS file. For more details the instruction is to
   look at the Git commit history
    Version 4.4.28
     * Add glibc-on-or1k (OpenRISC 1000) entry to libcrypt.minver.
       This was added in GNU libc 2.35.
    Version 4.4.27
     * Limit the maximum amount of rbytes to 64 bytes (512 bits) for
       yescrypt, gost-yescrypt, and scrypt.  Also reflect this limit
       in the documentation (issue #145).

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 770b4249e..cca81bb36 100644
--- a/lfs/libxcrypt
+++ b/lfs/libxcrypt
@@ -24,7 +24,7 @@
 
 include Config
 
-VER        = 4.4.26
+VER        = 4.4.28
 
 THISAPP    = libxcrypt-$(VER)
 DL_FILE    = $(THISAPP).tar.xz
@@ -47,7 +47,7 @@ objects = $(DL_FILE)
 
 $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
 
-$(DL_FILE)_MD5 = 34954869627f62f9992808b6cff0d0a9
+$(DL_FILE)_MD5 = 0b873e641ae201e5e7470cf791c0fe16
 
 install : $(TARGET)
 
-- 
2.35.1


             reply	other threads:[~2022-02-09 21:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-09 21:29 Adolf Belka [this message]
2022-02-11  8:50 ` Peter Müller

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=20220209212927.2754152-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