From: Willy Tarreau <willy@w.ods.org>
To: Syed Ahemed <kingkhan@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Patch for CVE-2004-1334 ???
Date: Mon, 23 Jan 2006 23:31:25 +0100 [thread overview]
Message-ID: <20060123223125.GU7142@w.ods.org> (raw)
In-Reply-To: <3d53b7120601230939p6e8906fbtb196ab49b9b028c5@mail.gmail.com>
Hi,
On Mon, Jan 23, 2006 at 11:09:49PM +0530, Syed Ahemed wrote:
> 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
> linux 2.4.28 on my production server.
I'm afraid 2.4-hf does not go that far backwards, it started at 2.4.29.
Git started even later. I've searched through http://linux.bkbits.net/
and I think that what you're looking for is here :
http://linux.bkbits.net:8080/linux-2.4/gnupatch@41b76e94BsJKm8jhVtyDat9ZM1dXXg
> If you think this question is stupid enough , then i would eventually
> write a patch for this .The trouble i have is on applying the patch
> cos my understanding of GPL is pretty confusing.
You don't have to worry, unless explicitly stated otherwise, patches
follow the same licence as the code they're for. So basically you can
apply a kernel patch from any other version to your kernel, and if you
know how to fix the bug by yourself (dangerous), that's fine too.
> Please point me to the patch for the above .
Please check above.
> Regards
> King khan
Regards,
Willy
next prev parent reply other threads:[~2006-01-23 22:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
[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=20060123223125.GU7142@w.ods.org \
--to=willy@w.ods.org \
--cc=kingkhan@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;
as well as URLs for NNTP newsgroup(s).