Wed Oct 11 06:37:21 UTC 202320231011063721

a/kernel-generic-6.1.57-x86_64-1.txz:  Upgraded.
a/kernel-huge-6.1.57-x86_64-1.txz:  Upgraded.
a/kernel-modules-6.1.57-x86_64-1.txz:  Upgraded.
d/kernel-headers-6.1.57-x86-1.txz:  Upgraded.
k/kernel-source-6.1.57-noarch-1.txz:  Upgraded.
n/c-ares-1.20.1-x86_64-1.txz:  Upgraded.
n/curl-8.4.0-x86_64-1.txz:  Upgraded.
  This update fixes security issues:
  Cookie injection with none file.
  SOCKS5 heap buffer overflow.
  For more information, see:
    https://curl.se/docs/CVE-2023-38546.html
    https://curl.se/docs/CVE-2023-38545.html
    https://www.cve.org/CVERecord?id=CVE-2023-38546
    https://www.cve.org/CVERecord?id=CVE-2023-38545
  (* Security fix *)
n/nghttp2-1.57.0-x86_64-1.txz:  Upgraded.
  This release has a fix to mitigate the HTTP/2 Rapid Reset vulnerability.
  For more information, see:
    https://github.com/nghttp2/nghttp2/security/advisories/GHSA-vx74-f528-fxqg
    https://www.cve.org/CVERecord?id=CVE-2023-44487
  (* Security fix *)
n/samba-4.19.1-x86_64-1.txz:  Upgraded.
  This is a security release in order to address the following defects:
  Unsanitized pipe names allow SMB clients to connect as root to existing
  unix domain sockets on the file system.
  SMB client can truncate files to 0 bytes by opening files with OVERWRITE
  disposition when using the acl_xattr Samba VFS module with the smb.conf
  setting "acl_xattr:ignore system acls = yes"
  An RODC and a user with the GET_CHANGES right can view all attributes,
  including secrets and passwords. Additionally, the access check fails
  open on error conditions.
  Calls to the rpcecho server on the AD DC can request that the server block
  for a user-defined amount of time, denying service.
  Samba can be made to start multiple incompatible RPC listeners, disrupting
  service on the AD DC.
  For more information, see:
    https://www.samba.org/samba/security/CVE-2023-3961.html
    https://www.samba.org/samba/security/CVE-2023-4091.html
    https://www.samba.org/samba/security/CVE-2023-4154.html
    https://www.samba.org/samba/security/CVE-2023-42669.html
    https://www.samba.org/samba/security/CVE-2023-42670.html
    https://www.cve.org/CVERecord?id=CVE-2023-3961
    https://www.cve.org/CVERecord?id=CVE-2023-4091
    https://www.cve.org/CVERecord?id=CVE-2023-4154
    https://www.cve.org/CVERecord?id=CVE-2023-42669
    https://www.cve.org/CVERecord?id=CVE-2023-42670
  (* Security fix *)
xap/mozilla-thunderbird-115.3.2-x86_64-1.txz:  Upgraded.
  This is a bugfix release.
  For more information, see:
    https://www.mozilla.org/en-US/thunderbird/115.3.2/releasenotes/
isolinux/initrd.img:  Rebuilt.
kernels/*:  Upgraded.
usb-and-pxe-installers/usbboot.img:  Rebuilt.

1 files changed, 7 insertions, 7 deletions

diff --git a/README.initrd b/README.initrd
index 58c3172dd..555fe05d6 100644
--- a/README.initrd
+++ b/README.initrd
@@ -1,7 +1,7 @@
 
 Slackware initrd mini HOWTO
 by Patrick Volkerding, volkerdi@slackware.com
-Fri Oct  6 21:13:34 UTC 2023
+Wed Oct 11 04:24:27 UTC 2023
 
 This document describes how to create and install an initrd, which may be 
 required to use the 4.x kernel. Also see "man mkinitrd".
@@ -33,15 +33,15 @@ flexible to ship a generic kernel and a set of kernel modules for it.
 
 The easiest way to make the initrd is to use the mkinitrd script included 
 in Slackware's mkinitrd package. We'll walk through the process of 
-upgrading to the generic 6.1.56 Linux kernel using the packages
+upgrading to the generic 6.1.57 Linux kernel using the packages
 found in Slackware's slackware/a/ directory.
 
 First, make sure the kernel, kernel modules, and mkinitrd package are 
 installed (the current version numbers might be a little different, so 
 this is just an example):
 
-  installpkg kernel-generic-6.1.56-x86_64-1.txz
-  installpkg kernel-modules-6.1.56-x86_64-1.txz
+  installpkg kernel-generic-6.1.57-x86_64-1.txz
+  installpkg kernel-modules-6.1.57-x86_64-1.txz
   installpkg mkinitrd-1.4.11-x86_64-33.txz
 
 Change into the /boot directory:
@@ -52,7 +52,7 @@ Now you'll want to run "mkinitrd". I'm using ext4 for my root filesystem,
 and since the disk controller requires no special support the ext4 module
 will be the only one I need to load:
 
-  mkinitrd -c -k 6.1.56 -m ext4
+  mkinitrd -c -k 6.1.57 -m ext4
 
 This should do two things. First, it will create a directory
 /boot/initrd-tree containing the initrd's filesystem. Then it will
@@ -61,10 +61,10 @@ you could make some additional changes in /boot/initrd-tree/ and
 then run mkinitrd again without options to rebuild the image. That's
 optional, though, and only advanced users will need to think about that.
 
-Here's another example: Build an initrd image using Linux 6.1.56
+Here's another example: Build an initrd image using Linux 6.1.57
 kernel modules for a system with an ext4 root partition on /dev/sdb3:
 
-  mkinitrd -c -k 6.1.56 -m ext4 -f ext4 -r /dev/sdb3
+  mkinitrd -c -k 6.1.57 -m ext4 -f ext4 -r /dev/sdb3
 
 
 4. Now that I've built an initrd, how do I use it?