From: Syed Ahemed <kingkhan@gmail.com>
To: Diego Calleja <diegocg@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Patch for CVE-2004-1334 ???
Date: Wed, 25 Jan 2006 14:26:51 +0530 [thread overview]
Message-ID: <3d53b7120601250056s77e876b6l2ac6781b8a9c9f00@mail.gmail.com> (raw)
In-Reply-To: <20060123191439.cfe5d61c.diegocg@gmail.com>
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 ?
I dont want to go to Gentoo for one patch , red hat for another
....and GOD knows how many sites .
Torvalds is the GOD of open source , but am i asking for too much :-)
On 1/23/06, Diego Calleja <diegocg@gmail.com> wrote:
> El Mon, 23 Jan 2006 23:09:49 +0530,
> Syed Ahemed <kingkhan@gmail.com> escribió:
>
> > Hi
> > I do know this community is busy with more important things , but i am
> > out of ideas/search on this one.
> > How do i get the patch for the CVE-2004-1334 ? I have an opensource
>
> Well, 2.4.32 fixes that bug and many others security. Any reason why you
> aren't using the latest version.
>
> You can find links to the changesets in the original security advisory
> from guninski (easy to find in google)
>
next prev parent reply other threads:[~2006-01-25 8:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-23 17:39 Syed Ahemed
2006-01-23 18:14 ` Diego Calleja
2006-01-25 8:56 ` Syed Ahemed [this message]
2006-01-25 22:09 ` Willy Tarreau
2006-01-26 12:27 ` Syed Ahemed
2006-01-23 22:31 ` Willy Tarreau
[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
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=3d53b7120601250056s77e876b6l2ac6781b8a9c9f00@mail.gmail.com \
--to=kingkhan@gmail.com \
--cc=diegocg@gmail.com \
--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®