public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@davemloft.net>
To: David Jacoby <dj@outpost24.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux kernel IGMP vulnerabilities, PATCH IS BROKEN!
Date: Wed, 15 Dec 2004 11:40:17 -0800	[thread overview]
Message-ID: <20041215114017.3a735aa8.davem@davemloft.net> (raw)
In-Reply-To: <41C0268B.2030708@outpost24.com>

On Wed, 15 Dec 2004 12:56:59 +0100
David Jacoby <dj@outpost24.com> wrote:

> Well it is, i booted on the old kernel and SSH worked perfect and then 
> on the new kernel with the patch i cant SSH, i dont even
> get an password prompt. I tried to ssh to more than one host aswell, i 
> also removed the key in .known_hosts but it still doesnt work.
> 
> Have you installed the patch?

I'm personally running it everywhere here, and ssh works fine.

There is no way that patch can change SSH behavior, you changed
something else when you updated your kernel.

  parent reply	other threads:[~2004-12-15 19:47 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 [this message]
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=20041215114017.3a735aa8.davem@davemloft.net \
    --to=davem@davemloft.net \
    --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