diff options
| author | Patrick J Volkerding <volkerdi@slackware.com> | 2018-12-06 04:38:11 +0000 |
|---|---|---|
| committer | Eric Hameleers <alien@slackware.com> | 2018-12-06 17:59:30 +0100 |
| commit | 37eaf40ce515cbb15e1b86fe5351a8e53efc0ede (patch) | |
| tree | 199d4b6d44ea50f05a7bddeff5d2789da22a185d /README.initrd | |
| parent | 03a61ce0245413a8759dd3391ca37dc25794f565 (diff) | |
| download | current-37eaf40ce515cbb15e1b86fe5351a8e53efc0ede.tar.gz | |
Thu Dec 6 04:38:11 UTC 201820181206043811
a/kernel-generic-4.19.7-x86_64-1.txz: Upgraded.
a/kernel-huge-4.19.7-x86_64-1.txz: Upgraded.
a/kernel-modules-4.19.7-x86_64-1.txz: Upgraded.
d/kernel-headers-4.19.7-x86-1.txz: Upgraded.
k/kernel-source-4.19.7-noarch-1.txz: Upgraded.
n/gnutls-3.6.5-x86_64-1.txz: Upgraded.
This update fixes a security issue:
Bleichenbacher-like side channel leakage in PKCS#1 1.5 verification and
padding oracle verification.
For more information, see:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-16868
(* Security fix *)
n/nettle-3.4.1-x86_64-1.txz: Upgraded.
This update fixes a security issue:
A Bleichenbacher type side-channel based padding oracle attack was found
in the way nettle handles endian conversion of RSA decrypted PKCS#1 v1.5
data. An attacker who is able to run a process on the same physical core
as the victim process, could use this flaw to extract plaintext or in some
cases downgrade any TLS connections to a vulnerable server.
For more information, see:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-16869
(* Security fix *)
isolinux/initrd.img: Rebuilt.
kernels/*: Upgraded.
usb-and-pxe-installers/usbboot.img: Rebuilt.
Diffstat (limited to 'README.initrd')
| -rw-r--r-- | README.initrd | 14 |
1 files changed, 7 insertions, 7 deletions
diff --git a/README.initrd b/README.initrd index b2193ed2..0d7c5929 100644 --- a/README.initrd +++ b/README.initrd @@ -1,7 +1,7 @@ Slackware initrd mini HOWTO by Patrick Volkerding, volkerdi@slackware.com -Sun Dec 2 00:47:20 UTC 2018 +Thu Dec 6 03:17:04 UTC 2018 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 4.19.6 Linux kernel using the packages +upgrading to the generic 4.19.7 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-4.19.6-x86_64-1.txz - installpkg kernel-modules-4.19.6-x86_64-1.txz + installpkg kernel-generic-4.19.7-x86_64-1.txz + installpkg kernel-modules-4.19.7-x86_64-1.txz installpkg mkinitrd-1.4.11-x86_64-8.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 4.19.6 -m ext4 + mkinitrd -c -k 4.19.7 -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 4.19.6 +Here's another example: Build an initrd image using Linux 4.19.7 kernel modules for a system with an ext4 root partition on /dev/sdb3: - mkinitrd -c -k 4.19.6 -m ext4 -f ext4 -r /dev/sdb3 + mkinitrd -c -k 4.19.7 -m ext4 -f ext4 -r /dev/sdb3 4. Now that I've built an initrd, how do I use it? |