public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Phil Oester <kernel@linuxace.com>
To: Chris Wright <chrisw@osdl.org>
Cc: David Jacoby <dj@outpost24.com>, linux-kernel@vger.kernel.org
Subject: Re: Linux kernel IGMP vulnerabilities, PATCH IS BROKEN!
Date: Wed, 15 Dec 2004 10:50:24 -0800	[thread overview]
Message-ID: <20041215185024.GA16990@linuxace.com> (raw)
In-Reply-To: <20041215103407.T469@build.pdx.osdl.net>

On Wed, Dec 15, 2004 at 10:34:07AM -0800, Chris Wright wrote:
> * David Jacoby (dj@outpost24.com) wrote:
> > The patch fucked something up, sorry for my language. Is there anyone 
> > else on
> > this list who has the patch installed?
> 
> Patch is fine.  I've used it and ssh quite a bit.  It only touches small
> bit of multicast specific code which isn't used at all during ssh session.

Yes, user is moving from unpatched 2.4.24 -> patched 2.6.9, and likely has
a pty config issue...

Phil


  reply	other threads:[~2004-12-15 18:53 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 [this message]
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

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=20041215185024.GA16990@linuxace.com \
    --to=kernel@linuxace.com \
    --cc=chrisw@osdl.org \
    --cc=dj@outpost24.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