From: Robert Hancock <hancockr@shaw.ca>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Patch for CVE-2004-1334 ???
Date: Wed, 25 Jan 2006 08:43:40 -0600 [thread overview]
Message-ID: <43D78E9C.1000804@shaw.ca> (raw)
In-Reply-To: <5yOFI-5CN-19@gated-at.bofh.it>
Syed Ahemed wrote:
> The simple reason we do not intend to use the latest version is we run
> some third party software which cant be front ported (pardon the slang
> ) to 2.4.29 and above.
> As for the changeset by guninski , i wish to ask about a one point
> source of applying all the patches for 2.4.28 .I mean shouldn't all
> the kernel security patches ( atleast the ones that have become CVE's)
> be a part of kernel.org .Since there isn't any what is the reason ?
It is "part of kernel.org", it's called 2.4.32. The kernel developers
can hardly be expected to release a patch for every vulnerability
against every possible kernel version ever released..
If you need guaranteed security patches against a specific version of
the kernel you should likely be using a distribution kernel and not a
vanilla kernel.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
next parent reply other threads:[~2006-01-25 14:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5ydZz-2G1-7@gated-at.bofh.it>
[not found] ` <5yetg-3us-31@gated-at.bofh.it>
[not found] ` <5yOFI-5CN-19@gated-at.bofh.it>
2006-01-25 14:43 ` Robert Hancock [this message]
2006-01-23 17:39 Patch for CVE-2004-1334 ??? Syed Ahemed
2006-01-23 18:14 ` Diego Calleja
2006-01-25 8:56 ` Syed Ahemed
2006-01-25 22:09 ` Willy Tarreau
2006-01-26 12:27 ` Syed Ahemed
2006-01-23 22:31 ` Willy Tarreau
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=43D78E9C.1000804@shaw.ca \
--to=hancockr@shaw.ca \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.