From: David Woodhouse <dwmw2@infradead.org>
To: bert hubert <ahu@ds9a.nl>
Cc: Mark Adler <madler@alumni.caltech.edu>,
Jesse Stockall <stockall@magma.ca>, Paul Jackson <pj@sgi.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] gcc 3.5 fixes
Date: Tue, 06 Jul 2004 07:46:56 +0100 [thread overview]
Message-ID: <1089096416.4636.1142.camel@imladris.demon.co.uk> (raw)
In-Reply-To: <20040706061149.GA3557@outpost.ds9a.nl>
On Tue, 2004-07-06 at 08:11 +0200, bert hubert wrote:
> On Mon, Jul 05, 2004 at 09:43:58PM -0700, Mark Adler wrote:
> > On Jul 5, 2004, at 8:51 PM, Jesse Stockall wrote:
> > >Did I miss something or are you saying that the version in the kernel
> > >has a security vulnerability?
> >
> > If the kernel has 1.1.3, then yes. You can get 1.1.4 here, which
> > remedies that vulnerability:
>
> I seem to recall that vulnerability was fixed in place, without upgrading to
> 1.1.4.
Indeed, but it's probably time we upgraded to 1.2.
--
dwmw2
next prev parent reply other threads:[~2004-07-06 6:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2e9is-5YT-1@gated-at.bofh.it>
[not found] ` <2e9iu-5YT-5@gated-at.bofh.it>
[not found] ` <2ecq2-80i-1@gated-at.bofh.it>
[not found] ` <7ab39013.0407042237.40ea9035@posting.google.com>
[not found] ` <20040705064010.C9BFB5F7AA@attila.bofh.it>
2004-07-05 16:51 ` Mark Adler
2004-07-05 21:44 ` Paul Jackson
2004-07-06 1:16 ` Mark Adler
2004-07-06 1:45 ` Paul Jackson
2004-07-06 3:51 ` Jesse Stockall
2004-07-06 4:43 ` Mark Adler
2004-07-06 6:11 ` bert hubert
2004-07-06 6:46 ` David Woodhouse [this message]
2004-07-06 15:02 ` Mark Adler
2004-07-04 6:58 Anton Blanchard
2004-07-04 7:01 ` Anton Blanchard
2004-07-04 7:07 ` Anton Blanchard
2004-07-04 10:24 ` Bartlomiej Zolnierkiewicz
2004-07-04 11:04 ` Anton Blanchard
2004-07-06 15:28 ` Randy.Dunlap
2004-07-11 10:23 ` Anton Blanchard
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=1089096416.4636.1142.camel@imladris.demon.co.uk \
--to=dwmw2@infradead.org \
--cc=ahu@ds9a.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=madler@alumni.caltech.edu \
--cc=pj@sgi.com \
--cc=stockall@magma.ca \
/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®