From ab672bcf47dca57cfce72407176dd6460c3397b7 Mon Sep 17 00:00:00 2001 From: Patrick J Volkerding Date: Thu, 23 Jun 2022 05:30:51 +0000 Subject: Thu Jun 23 05:30:51 UTC 2022 a/kernel-generic-5.18.6-x86_64-1.txz: Upgraded. a/kernel-huge-5.18.6-x86_64-1.txz: Upgraded. a/kernel-modules-5.18.6-x86_64-1.txz: Upgraded. a/openssl-solibs-1.1.1p-x86_64-1.txz: Upgraded. ap/sudo-1.9.11p3-x86_64-1.txz: Upgraded. d/kernel-headers-5.18.6-x86-1.txz: Upgraded. k/kernel-source-5.18.6-noarch-1.txz: Upgraded. l/espeak-ng-1.51.1-x86_64-1.txz: Upgraded. l/libidn-1.40-x86_64-1.txz: Upgraded. l/mlt-7.8.0-x86_64-1.txz: Upgraded. l/openal-soft-1.22.1-x86_64-1.txz: Upgraded. l/pulseaudio-16.1-x86_64-1.txz: Upgraded. l/speex-1.2.1-x86_64-1.txz: Upgraded. l/speexdsp-1.2.1-x86_64-1.txz: Upgraded. n/ca-certificates-20220622-noarch-1.txz: Upgraded. This update provides the latest CA certificates to check for the authenticity of SSL connections. n/openssl-1.1.1p-x86_64-1.txz: Upgraded. In addition to the c_rehash shell command injection identified in CVE-2022-1292, further circumstances where the c_rehash script does not properly sanitise shell metacharacters to prevent command injection were found by code review. When the CVE-2022-1292 was fixed it was not discovered that there are other places in the script where the file names of certificates being hashed were possibly passed to a command executed through the shell. For more information, see: https://www.openssl.org/news/secadv/20220621.txt https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-2068 (* Security fix *) x/ibus-table-1.16.9-x86_64-1.txz: Upgraded. isolinux/initrd.img: Rebuilt. kernels/*: Upgraded. usb-and-pxe-installers/usbboot.img: Rebuilt. --- README.initrd | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) (limited to 'README.initrd') diff --git a/README.initrd b/README.initrd index e4e259560..db787423a 100644 --- a/README.initrd +++ b/README.initrd @@ -1,7 +1,7 @@ Slackware initrd mini HOWTO by Patrick Volkerding, volkerdi@slackware.com -Thu Jun 16 23:27:00 UTC 2022 +Thu Jun 23 05:18:24 UTC 2022 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 5.18.5 Linux kernel using the packages +upgrading to the generic 5.18.6 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-5.18.5-x86_64-1.txz - installpkg kernel-modules-5.18.5-x86_64-1.txz + installpkg kernel-generic-5.18.6-x86_64-1.txz + installpkg kernel-modules-5.18.6-x86_64-1.txz installpkg mkinitrd-1.4.11-x86_64-29.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 5.18.5 -m ext4 + mkinitrd -c -k 5.18.6 -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 5.18.5 +Here's another example: Build an initrd image using Linux 5.18.6 kernel modules for a system with an ext4 root partition on /dev/sdb3: - mkinitrd -c -k 5.18.5 -m ext4 -f ext4 -r /dev/sdb3 + mkinitrd -c -k 5.18.6 -m ext4 -f ext4 -r /dev/sdb3 4. Now that I've built an initrd, how do I use it? -- cgit v1.2.3-65-gdbad