From: "Massimo Cetra" <mcetra@navynet.it>
To: "'Barry K. Nathan'" <barryn@pobox.com>,
"'O.Sezer'" <sezeroz@ttnet.net.tr>
Cc: <linux-kernel@vger.kernel.org>, <marcelo.tosatti@cyclades.com>
Subject: RE: Linux 2.4.28-rc4
Date: Fri, 19 Nov 2004 01:10:32 +0100 [thread overview]
Message-ID: <20041119001033.B25D48400A@server1.navynet.it> (raw)
In-Reply-To: <20041118204841.GA11682@ip68-4-98-123.oc.oc.cox.net>
> Marcelo and I discussed this via private e-mail; it's in the
> queue for 2.4.29-pre. I think in the end we both agreed that
> it's too late in the
> 2.4.28 cycle to include these patches.
>
> -Barry K. Nathan <barryn@pobox.com>
Why such a decision ?
Do you think that it is not exploitable or at least not in a short time ?
I don't think 2.4.29 will see the light in a short time so, unless there are
serious problems arising from these patches (and 2.6 should be affected
too), I think that for the sake of security it may be worthy and clever
includind these patches (and delay 2.4.28 for some days...)
M$ is waiting for a gold occasion to shot on linux.
A known buffer overflow, not patched soon, may be used against linux and,
what interest me more, we could avoid updating kernels on tons pf production
servers for something which could be patched before.
Massimo Cetra
next prev parent reply other threads:[~2004-11-19 0:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-17 9:21 Linux 2.4.28-rc4 O.Sezer
2004-11-18 20:48 ` Barry K. Nathan
2004-11-18 17:58 ` Marcelo Tosatti
2004-11-19 0:10 ` Massimo Cetra [this message]
2004-11-19 0:25 ` Chris Wright
2004-11-19 8:03 ` Massimo Cetra
2004-11-19 21:34 ` Barry K. Nathan
-- strict thread matches above, loose matches on Subject: below --
2004-11-16 20:41 Marcelo Tosatti
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=20041119001033.B25D48400A@server1.navynet.it \
--to=mcetra@navynet.it \
--cc=barryn@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
--cc=sezeroz@ttnet.net.tr \
/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