linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcelo Tosatti <marcelo@conectiva.com.br>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: John Bradford <john@grabjohn.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	torvalds@osdl.org
Subject: Re: Linux v2.6.0-test1
Date: Mon, 14 Jul 2003 10:56:59 -0300 (BRT)	[thread overview]
Message-ID: <Pine.LNX.4.55L.0307141055530.18257@freak.distro.conectiva> (raw)
In-Reply-To: <1058182417.561.47.camel@dhcp22.swansea.linux.org.uk>



On Mon, 14 Jul 2003, Alan Cox wrote:

> On Llu, 2003-07-14 at 12:39, John Bradford wrote:
> > > > > The point of the test versions is to make more people realize that they
> > > > > need testing
> > > >
> > > > Are all the known security issues in 2.4 now fixed in 2.6.0-test1?
> > >
> > > No, and several more have been added in 2.6-test only.
> >
> > As far as I know, they are only information disclosure ones, not
> > directly exploitable vulnerabilities, or am I wrong?
>
> Last time I checked there were remote DoS attacks and local root attacks
> present in 2.5.7x
>
> > > > This has been the only major reason for keeping of most of my
> > > > production machines running 2.4 for quite a while.  If not, can we get
> > > > the fixes in at the earliest opportunity?
> > >
> > > Sure.. send the fixes to Linus
> >
> > Is anybody even keeping track of this, though?  Picking thorough LKML
> > to see what did and didn't go in doesn't seem particularly exciting to
> > me.
>
> Then you'll just have to wait a few months

I will start looking at 2.4 security fixes which are not applied in 2.6.

If someone is already doing that, please tell me.

  reply	other threads:[~2003-07-14 13:47 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-14 11:39 John Bradford
2003-07-14 11:33 ` Alan Cox
2003-07-14 13:56   ` Marcelo Tosatti [this message]
2003-07-14 15:07     ` Alan Cox
2003-07-14 16:44       ` Marcelo Tosatti
  -- strict thread matches above, loose matches on Subject: below --
2003-07-15  7:52 Dirk Meul
2003-07-16  6:32 ` Martin Schlemmer
2003-07-14 11:50 John Bradford
2003-07-14 11:53 ` Dave Jones
2003-07-14 12:00   ` William Lee Irwin III
2003-07-14 12:39     ` Alan Cox
2003-07-14 12:47       ` William Lee Irwin III
2003-07-14 12:47         ` Alan Cox
2003-07-14 12:40 ` Alan Cox
2003-07-14 16:55 ` Kurt Wall
2003-07-14 11:01 John Bradford
2003-07-14 11:15 ` Alan Cox
2003-07-14  3:59 Linus Torvalds
2003-07-15  4:11 ` Matt Reppert
2003-07-15 10:56   ` Dave Jones
2003-07-15 17:38     ` Dominik Brodowski
2003-07-15 18:11       ` Dave Jones
2003-05-22 20:12 DMA gone on ALI 1533 Peter
2003-07-14  7:26 ` Linux v2.6.0-test1 Peter

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=Pine.LNX.4.55L.0307141055530.18257@freak.distro.conectiva \
    --to=marcelo@conectiva.com.br \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=john@grabjohn.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.org \
    --subject='Re: Linux v2.6.0-test1' \
    /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

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).