Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.security > #5116 > unrolled thread
| Started by | praeponiertesNichts <praeponiertesNichts@web.de> |
|---|---|
| First post | 2016-11-19 11:10 +0100 |
| Last post | 2016-11-19 12:20 +0100 |
| Articles | 2 — 2 participants |
Back to article view | Back to linux.debian.security
Wheezy -- Dirty Cow praeponiertesNichts <praeponiertesNichts@web.de> - 2016-11-19 11:10 +0100
Re: Wheezy -- Dirty Cow Corvin Mcpherson <corvin455@gmail.com> - 2016-11-19 12:20 +0100
| From | praeponiertesNichts <praeponiertesNichts@web.de> |
|---|---|
| Date | 2016-11-19 11:10 +0100 |
| Subject | Wheezy -- Dirty Cow |
| Message-ID | <sFaKR-3xB-7@gated-at.bofh.it> |
[Multipart message — attachments visible in raw view] — view raw
Hey there I have followed the discussion regarding the issue of fixing the dirtyCow thing, but I just wanted to make sure that I get things right. I have a server with wheezy and this is what I get for > uname -a 3.2.0-4-amd64 #1 SMP Debian 3.2.73-2+deb7u2 x86_64 GNU/Linux As far as I can see it, I will only get the appropriate kernel version via backports. These would be my sources.list deb http://ftp.de.debian.org/debian/ wheezy main deb-src http://ftp.de.debian.org/debian/ wheezy main deb http://security.debian.org/ wheezy/updates main deb-src http://security.debian.org/ wheezy/updates main # wheezy-updates, previously known as 'volatile' deb http://ftp.de.debian.org/debian/ wheezy-updates main deb-src http://ftp.de.debian.org/debian/ wheezy-updates main ############## What I need to do would be to add the backports: deb http://ftp.debian.org/debian/ wheezy-backports main contrib non-free deb-src http://ftp.debian.org/debian/ wheezy-backports main contrib non-free |apt-get update| |apt-cache search linux-image| |apt-cache search linux-headers| |apt-get install -t wheezy-backports linux-image-amd64 linux-headers-amd64| | followed by a reboot.| |Would this fix it?| |regards| |pn |
[toc] | [next] | [standalone]
| From | Corvin Mcpherson <corvin455@gmail.com> |
|---|---|
| Date | 2016-11-19 12:20 +0100 |
| Message-ID | <sFbQB-4ep-1@gated-at.bofh.it> |
| In reply to | #5116 |
[Multipart message — attachments visible in raw view] — view raw
Hey https://security-tracker.debian.org/tracker/CVE-2016-5195 Wheezy has its own applied patch on the 3.2.x kernel So you *should* probably be looking to update to kernel 3.2.82-1 instead of trying to install the Jessie kernel You *should* probably just leave the apt sources list alone and... Update the package list: $ apt-get update Perform a package upgrade: $ apt-get upgrade And then your reboot Then after reboot I would confirm that you are running 3.2.82-1 and you should be good to go if so. Thanks On Sat, Nov 19, 2016 at 05:03 praeponiertesNichts < praeponiertesNichts@web.de> wrote: > Hey there > > I have followed the discussion regarding the issue of fixing the dirtyCow > thing, but I just wanted to make sure that I get things right. > > I have a server with wheezy and this is what I get for > > > uname -a > > 3.2.0-4-amd64 #1 SMP Debian 3.2.73-2+deb7u2 x86_64 GNU/Linux > As far as I can see it, I will only get the appropriate kernel version via > backports. > > These would be my sources.list > > deb http://ftp.de.debian.org/debian/ wheezy main > deb-src http://ftp.de.debian.org/debian/ wheezy main > > deb http://security.debian.org/ wheezy/updates main > deb-src http://security.debian.org/ wheezy/updates main > > # wheezy-updates, previously known as 'volatile' > deb http://ftp.de.debian.org/debian/ wheezy-updates main > deb-src http://ftp.de.debian.org/debian/ wheezy-updates main > > ############## > > What I need to do would be to add the backports: > > deb http://ftp.debian.org/debian/ wheezy-backports main contrib non-free > deb-src http://ftp.debian.org/debian/ wheezy-backports main contrib > non-free > > apt-get update > apt-cache search linux-image > apt-cache search linux-headers > apt-get install -t wheezy-backports linux-image-amd64 linux-headers-amd64 > > > followed by a reboot. > > Would this fix it? > > regards > > pn >
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.security
csiph-web