From: "Jesper Juhl" <jesper.juhl@gmail.com>
To: "Manuel Reimer" <Manuel.Spam@nurfuerspam.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Will there be security updates for 2.6.17 kernels?
Date: Thu, 14 Dec 2006 16:10:55 +0100 [thread overview]
Message-ID: <9a8748490612140710o478bf73p7efc607f545cf499@mail.gmail.com> (raw)
In-Reply-To: <elrop2$vdl$1@sea.gmane.org>
On 14/12/06, Manuel Reimer <Manuel.Spam@nurfuerspam.de> wrote:
> Hello,
>
> my problem is, that the slackware maintainers decided to use kernel
> 2.6.17. Here is their comment, they posted to the changelog:
>
<snip>
>
> They had a 2.6.16 kernel in /extra before and as far as I know the
> 2.6.16 kernel series still gets security updates.
>
> Is this also the case for 2.6.17 kernels?
No, that is not planned. 2.6.16.x is an exception. -stable kernels
(those with 2.6.x.y versions) are only released for the latest stable
2.6.x kernel. So currently that's 2.6.19 and as soon as 2.6.20 comes
out there will not be any more 2.6.19.x, only 2.6.20.x - I hope
that's clear...
>will there be an update if
> there is an security hole in the latest 2.6.17 kernel?
>
No. If the problem was also in the latest stable kernel (currently
2.6.19.1) then a fix would go into 2.6.19.2 and users can then upgrade
to that kernel. If 2.6.19.1 is not vulnerable, then everything is fine
as users of old 2.6.17 kernels can just upgrade to 2.6.19.1
> The problem is, that the slackware team doesn't patch anything on their
> own. They always wait for the update done by the author, if the bug
> isn't very critical. This means they will stay forever with their
> current version of the 2.6.17 kernel, if there will be no updates in
> future.
>
Not true. Slackware updates the kernel to fix security issues - this
has been the case in the past and i don't see why it would change in
the future.
> If there will be no updates for 2.6.17 in future: Are there already
> security holes in 2.6.17?
probably.
>Could someone please give two examples? I need
> informations, to be able to contact the slackware team, to request a
> "downgrade" to 2.6.16.
>
Ehh, you wouldn't want to do that. You'd want to encourage an upgrade
to 2.6.19.1 instead.
--
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html
next prev parent reply other threads:[~2006-12-14 15:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-14 14:59 Manuel Reimer
2006-12-14 15:10 ` Jesper Juhl [this message]
2006-12-14 19:33 ` Manuel Reimer
2006-12-15 17:27 ` Bill Davidsen
2006-12-14 20:18 Mario Vanoni
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9a8748490612140710o478bf73p7efc607f545cf499@mail.gmail.com \
--to=jesper.juhl@gmail.com \
--cc=Manuel.Spam@nurfuerspam.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®