public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: Lukasz Trabinski <lukasz@wsisiz.edu.pl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux kernel IGMP vulnerabilities
Date: Thu, 16 Dec 2004 08:24:45 -0200	[thread overview]
Message-ID: <20041216102445.GB8246@logos.cnet> (raw)
In-Reply-To: <200412160008.iBG0895a008498@lt.wsisiz.edu.pl>

On Thu, Dec 16, 2004 at 01:08:09AM +0100, Lukasz Trabinski wrote:
> In article <20041215.180839.93043538.yoshfuji@linux-ipv6.org> you wrote:
> > In article <41BFF931.6030205@outpost24.com> (at Wed, 15 Dec 2004 09:43:29 +0100), David Jacoby <dj@outpost24.com> says:
> > 
> >> Any advice about how people can patch this security issue?
> > 
> > http://linux.bkbits.net:8080/linux-2.6/cset@41bf39b1RGfvOMInGewwDyzfcuL2OQ
> 
> When we can expect officall realase of 2.4.X and 2.6.X with this patch?

2.4.29 final should be released about end of January.

      reply	other threads:[~2004-12-16 13:21 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-15  8:43 Linux kernel IGMP vulnerabilities David Jacoby
2004-12-15  9:08 ` YOSHIFUJI Hideaki / 吉藤英明
2004-12-15 11:49   ` Linux kernel IGMP vulnerabilities, PATCH IS BROKEN! David Jacoby
2004-12-15 11:54     ` Marc-Christian Petersen
2004-12-15 11:56       ` David Jacoby
     [not found]         ` <20041215120418.GA9049@tufnell.lon1.poggs.net>
2004-12-15 12:11           ` David Jacoby
2004-12-15 14:20             ` YOSHIFUJI Hideaki / 吉藤英明
2004-12-15 18:34             ` Chris Wright
2004-12-15 18:50               ` Phil Oester
2004-12-15 19:40         ` David S. Miller
2004-12-16  6:16           ` Willy Tarreau
2004-12-16 22:53         ` Bill Davidsen
2004-12-17  7:27           ` David Jacoby
2004-12-16  0:08   ` Linux kernel IGMP vulnerabilities Lukasz Trabinski
2004-12-16 10:24     ` Marcelo Tosatti [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=20041216102445.GB8246@logos.cnet \
    --to=marcelo.tosatti@cyclades.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lukasz@wsisiz.edu.pl \
    /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