-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

[slackware-security]  Slackware 14.2 kernel (SSA:2018-208-01)

New kernel packages are available for Slackware 14.2 to fix security issues.


Here are the details from the Slackware 14.2 ChangeLog:
+--------------------------+
patches/packages/linux-4.4.144/*:  Upgraded.
  This kernel update enables additional mitigations for spectre_v2 (IBPB and
  IBRS_FW). It also enables reporting on the Speculative Store Bypass
  vulnerability (aka GPZ Variant 4) which affects Intel processors and must
  be patched with a microcode update.
  To see the status of CPU vulnerability mitigations on your system, look at
  the files in: /sys/devices/system/cpu/vulnerabilities
  In addition, these kernels enable SMB2. Here's the complete list of kernel
  config changes from the previous 4.4.132:
    -X86_DEBUG_STATIC_CPU_HAS n
     CIFS_SMB2 n -> y
    +CC_OPTIMIZE_FOR_PERFORMANCE y
    +CIFS_SMB311 n
    +X86_FAST_FEATURE_TESTS y
  Be sure to upgrade your initrd after upgrading the kernel packages.
  If you use lilo to boot your machine, be sure lilo.conf points to the correct
  kernel and initrd and run lilo as root to update the bootloader.
  If you use elilo to boot your machine, you should run eliloconfig to copy the
  kernel and initrd to the EFI System Partition.
  For more information, see:
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-3639
  (* Security fix *)
+--------------------------+


Where to find the new packages:
+-----------------------------+

Thanks to the friendly folks at the OSU Open Source Lab
(https://osuosl.org/) for donating FTP and rsync hosting
to the Slackware project!  :-)

Also see the "Get Slack" section on http://www.slackware.com/ for
additional mirror sites near you.

Updated packages for Slackware 14.2:
 

Updated packages for Slackware x86_64 14.2:


MD5 signatures:
+-------------+

Slackware 14.2 packages:
78b4734f9898dceb88c85e2428ecb229  kernel-firmware-20180727_b01151b-noarch-1.txz
c6d60676defaf0aff665e16d9c2a7fb5  kernel-generic-4.4.144-i586-1.txz
cd9e3723a06cbc3f836ceda50568ee20  kernel-generic-smp-4.4.144_smp-i686-1.txz
b3c43f455774ddd33247759baab252aa  kernel-headers-4.4.144_smp-x86-1.txz
cc87a7baeb407f080011625435a7e268  kernel-huge-4.4.144-i586-1.txz
f081add71fe7909a49bc84becccc29ee  kernel-huge-smp-4.4.144_smp-i686-1.txz
061a686e01ba27e94e67d0163f9fec7f  kernel-modules-4.4.144-i586-1.txz
d54f9e6eb5271d88bf80555f250cf742  kernel-modules-smp-4.4.144_smp-i686-1.txz
526b09e6aa33987cc1067dbfb418e414  kernel-source-4.4.144_smp-noarch-1.txz


Slackware x86_64 14.2 packages:
78b4734f9898dceb88c85e2428ecb229  kernel-firmware-20180727_b01151b-noarch-1.txz
ad06c7a0fdada92f42ec52759fe4f037  kernel-generic-4.4.144-x86_64-1.txz
411d9c7db2167177ee97a8f7cbf4366a  kernel-headers-4.4.144-x86-1.txz
f5176e27d85d80049532811423f8616b  kernel-huge-4.4.144-x86_64-1.txz
847b5f06e3cd0eccce0a93b98412ede6  kernel-modules-4.4.144-x86_64-1.txz
f8efe4ac11ac27114291238fafd7c406  kernel-source-4.4.144-noarch-1.txz


Installation instructions:
+------------------------+

Upgrade the packages as root:
# upgradepkg kernel-*.txz

If you are using an initrd, you'll need to rebuild it.

For a 32-bit SMP machine, use this command (substitute the appropriate
kernel version if you are not running Slackware 14.2):
# /usr/share/mkinitrd/mkinitrd_command_generator.sh -k 4.4.144-smp | bash

For a 64-bit machine, or a 32-bit uniprocessor machine, use this command
(substitute the appropriate kernel version if you are not running
Slackware 14.2):
# /usr/share/mkinitrd/mkinitrd_command_generator.sh -k 4.4.144 | bash

Please note that "uniprocessor" has to do with the kernel you are running,
not with the CPU.  Most systems should run the SMP kernel (if they can)
regardless of the number of cores the CPU has.  If you aren't sure which
kernel you are running, run "uname -a".  If you see SMP there, you are
running the SMP kernel and should use the 4.4.144-smp version when running
mkinitrd_command_generator.  Note that this is only for 32-bit -- 64-bit
systems should always use 4.4.144 as the version.

If you are using lilo or elilo to boot the machine, you'll need to ensure
that the machine is properly prepared before rebooting.

If using LILO:
By default, lilo.conf contains an image= line that references a symlink
that always points to the correct kernel.  No editing should be required
unless your machine uses a custom lilo.conf.  If that is the case, be sure
that the image= line references the correct kernel file.  Either way,
you'll need to run "lilo" as root to reinstall the boot loader.

If using elilo:
Ensure that the /boot/vmlinuz symlink is pointing to the kernel you wish
to use, and then run eliloconfig to update the EFI System Partition.


+-----+