From: Arjan van de Ven <arjanv@redhat.com>
To: Dale Amon <amon@vnl.com>, linux-kernel@vger.kernel.org
Subject: Re: Question on LFS in Redhat
Date: Thu, 25 Dec 2003 09:35:29 +0100 [thread overview]
Message-ID: <20031225083529.GC29678@devserv.devel.redhat.com> (raw)
In-Reply-To: <20031225010925.GG4987@vnl.com>
[-- Attachment #1: Type: text/plain, Size: 1271 bytes --]
On Thu, Dec 25, 2003 at 01:09:25AM +0000, Dale Amon wrote:
> On Wed, Dec 24, 2003 at 09:49:03AM +0100, Arjan van de Ven wrote:
> > You really shouldn't be running a 2.4.16 kernel (not without the latest
> > security patches for such a kernel from a distro) given the amount of security issues
> > fixed since... and since I don't think any distro ever shipped 2.4.16 (some
> > shipped 2.4.17, a bunch shipped 2.4.18 but even RH doesn't do patches for
> > that 2.4.18 tree anymore since they have been obsoleted by 2.4.20 and newer
> > kernels).
>
> Not really my choice... and from what you say I'd better
> not *touch* their stock kernel if I a project for which I
> specced that box happens.
>
> Also, fresh feedback from the Consensys is that:
>
> "Just to be precise - As of today the kernel
> is 2.4.18-i59smp #1"
can you ask them for the full source of this (including that of derived
works they include in it) ? I'd be curious what stuff they include
> So that is a little better but still a little out
> of date. I'm not terribly worried about the local
> exploit because you don't tend to want to allow external
> login accounts on things on your SAN's...
you forgot the remote hash-collision DoS issues in 2.4.18 etc etc
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2003-12-25 8:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-23 15:10 Question on LFS in Redhat Dale Amon
2003-12-23 15:38 ` Arjan van de Ven
2003-12-23 23:58 ` Dale Amon
2003-12-24 0:24 ` Mike Fedyk
2003-12-24 8:49 ` Arjan van de Ven
2003-12-25 1:09 ` Dale Amon
2003-12-25 8:35 ` Arjan van de Ven [this message]
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=20031225083529.GC29678@devserv.devel.redhat.com \
--to=arjanv@redhat.com \
--cc=amon@vnl.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