LinuxQuestions.org - kernel security update x86

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - kernel security update x86_64 (https://www.linuxquestions.org/questions/slackware-14/kernel-security-update-x86_64-a-774820/)

kernel security update x86_64

Hi everyone!

Im not the most experienced slackware user but I can cope :)

Before I run this Update I wanted to ask you pros some questions.

Quote:

Here are the details from the Slackware 13.0 ChangeLog:
+--------------------------+
Tue Dec 8 20:44:44 UTC 2009
patches/packages/linux-2.6.29.6-3/:
Added new kernels and kernel packages with a patch for CVE-2009-1298,
a kernel bug where oversized IP packets cause a NULL pointer dereference
and immediate hang.
For more information, see:
http://cve.mitre.org/cgi-bin/cvename...=CVE-2009-1298
http://lkml.org/lkml/2009/11/25/104
Be sure to reinstall LILO after upgrading the kernel packages.
(* Security fix *)

Im sure you can clear my clouds.

Im running a multiboot system with a boot partition which runs grub and chainloads into each linux distribution. On each system partition I installed the grub for its own distribution.

If I want to boot Slackware:
boot partition: /dev/sda1 chainloads into lilo on /dev/sda8 which boots into slackware on /dev/sda8

Im not familiar with lilo.

1. The kernel update:
which files would I install?
/boot
contains:

Code:

# ls /boot/

README.initrd                boot.0808                config-huge-2.6.29.6  slack.bmp

System.map                  boot_message.txt        diag1.img            vmlinuz

System.map-generic-2.6.29.6  config                  diag2.img            vmlinuz-generic-2.6.29.6

System.map-huge-2.6.29.6    config-generic-2.6.29.6  map                  vmlinuz-huge-2.6.29.6

/etc/lilo.conf:

Code:

# LILO configuration file

# generated by 'liloconfig'

#

# Start LILO global section

boot = /dev/sda8

#compact        # faster, but won't work on all systems.

# Boot BMP Image.

# Bitmap in BMP format: 640x480x8

  bitmap = /boot/slack.bmp

# Menu colors (foreground, background, shadow, highlighted

# foreground, highlighted background, highlighted shadow):

  bmp-colors = 255,0,255,0,255,0

# Location of the option table: location x, location y, number of

# columns, lines per column (max 15), "spill" (this is how many

# entries must be in the first column before the next begins to

# be used.  We don't specify it here, as there's just one column.

  bmp-table = 60,6,1,16

# Timer location x, timer location y, foreground color,

# background color, shadow color.

  bmp-timer = 65,27,0,255

# Standard menu.

# Or, you can comment out the bitmap menu above and

# use a boot message with the standard menu:

#message = /boot/boot_message.txt



# Append any additional kernel parameters:

append=" vt.default_utf8=0"

prompt

timeout = 50

# VESA framebuffer console @ 1024x768x256

vga = 773

# Normal VGA console

# vga = normal

# VESA framebuffer console @ 1024x768x64k

# vga=791

# VESA framebuffer console @ 1024x768x32k

# vga=790

# VESA framebuffer console @ 1024x768x256

# vga=773

# VESA framebuffer console @ 800x600x64k

# vga=788

# VESA framebuffer console @ 800x600x32k

# vga=787

# VESA framebuffer console @ 800x600x256

# vga=771

# VESA framebuffer console @ 640x480x64k

# vga=785

# VESA framebuffer console @ 640x480x32k

# vga=784

# VESA framebuffer console @ 640x480x256

# vga=769

# ramdisk = 0    # paranoia setting

# End LILO global section

# Linux bootable partition config begins

image = /boot/vmlinuz

  root = /dev/sda8

  label = Slackware

  read-only  # Partitions should be mounted read-only for checking

# Linux bootable partition config ends

So, I believe I run the generic kernel?

How would I go about?

My thoughts:
I download:
kernel-firmware-2.6.29.6-noarch-3.txz
kernel-generic-2.6.29.6-x86_64-3.txz
kernel-headers-2.6.29.6-x86-3.txz
kernel-huge-2.6.29.6-x86_64-3.txz
kernel-modules-2.6.29.6-x86_64-3.txz
kernel-source-2.6.29.6-noarch-3.txz

... thats all I need?

and I just install those packages using

Code:

installpkg

Do I have to go into the subdirectory
generic.s
huge.s
speakup.s
and download those images, too?

If that install is done, do I have to do a lilo update? It boots /boot/vmlinuz. So that would be the updated kernel anyway.

Are my proceedings correct?

Thx for any help!
I really dig Slackware
Pluribootent

You're making it too complicated.

Use "su -" to become root
Use slackpkg to install the updated kernel packages:
Edit /etc/slackpkg/mirrors to select a close mirror for your exact version of Slackware
Then run these in order:
# slackpkg update
# slackpkg upgrade-all
# lilo

And how about the initrd and (if applicable) the nvidia drivers?

They're OK and still fully operational after the update. No problems.

Quote:

Originally Posted by Pluribootent (Post 3787180)

My thoughts:
I download:
kernel-firmware-2.6.29.6-noarch-3.txz
kernel-generic-2.6.29.6-x86_64-3.txz
kernel-headers-2.6.29.6-x86-3.txz
kernel-huge-2.6.29.6-x86_64-3.txz
kernel-modules-2.6.29.6-x86_64-3.txz
kernel-source-2.6.29.6-noarch-3.txz

... thats all I need?

and I just install those packages using

Code:

installpkg

Those packages are all you need. If you download them you can use upgradepkg to upgrade to the new kernel packages. Or you can use slackpkg as has been suggested.
Be sure to rerun lilo after updating the kernel packages as it says on the Slackware changelogs page.

Slackpkg offers to run lilo after installing the updates.

Quote:

Originally Posted by cmk77 (Post 3787664)

And how about ... the nvidia drivers?

better to reinstall them, kernel module part was built during their installation for the older kernel version.

The nvidia driver's working on mine, without reinstalling.

It's the same kernel version, with a patch:
old: 2.6.29.6-x86_64-2
new: 2.6.29.6-x86_64-3

Great, Thanx all for your help and comments.

The update went fine with slackpkg. I didnt know about this tool. Maybe its new? Anyway good to have it.
The kernel got installed ok.
The nvidia drivers still work. Without reinstalling.
Running lilo was no problem.

But I have one question about lilo:
It didnt ask me where I want lilo to install to. I need lilo on the systempartition not in the MBR. I installed it to the systempartition when I installed Slackware64_13. So I guess its somewhere mentioned in the /etc/lilo.conf. Is that correct?
So I dont have toworry in the future, because lilo will always remember to be installed to the system partition not the MBR?

(maybe a n00b question, but I want to find out how it works)

Thanks alot!

That was misleading in the ChangeLog where it said "reinstall lilo", it meant rerun.

Quote:

Originally Posted by brianL (Post 3787698)

It's the same kernel version, with a patch:
old: 2.6.29.6-x86_64-2
new: 2.6.29.6-x86_64-3

yes, but it has been rebuilt so I don't think nvidia drivers will work fully ok because they have been built against the old kernel: if they do it's just a coincidence, I think.
sorry, cannot verify on my slack 'cause i use a custom 2.6.32 kernel.

Well, I've got 6 twirly-whirly desktops in a cube, exploding windows, and all that crap. :D And there's been no sign of a complaint in the boot up messages.

For what it's worth, my nvidia driver is also working just fine after the kernel upgrade. I did not have to reinstall the nvidia driver. This includes gaming with games like Nexuiz and Blob Wars.

It is as it should be. It's the same kernel, compiled with the same compiler of the same version, there's just a single source line modified. Kernel modules should not require recompilation.