From: David Jacoby <dj@outpost24.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Linux kernel IGMP vulnerabilities, PATCH IS BROKEN!
Date: Fri, 17 Dec 2004 08:27:50 +0100 [thread overview]
Message-ID: <41C28A76.4080905@outpost24.com> (raw)
In-Reply-To: <41C211E3.8040601@tmr.com>
Bill Davidsen wrote:
> David Jacoby wrote:
>
>> Marc-Christian Petersen wrote:
>>
>>> On Wednesday 15 December 2004 12:49, David Jacoby wrote:
>>>
>>>
>>>
>>>> Anyone else tried to apply this patch? The patch does work but not
>>>> properly.
>>>> I guess the machie is secure against the DoS attack but after i
>>>> installed the patch
>>>> i cant use SSH.When i tryed to SSH i didnt get any password prompt.
>>>> user@autopsia:~$ ssh user@192.168.0.1
>>>> Permission denied, please try again.
>>>> Permission denied, please try again.
>>>> Permission denied (publickey,password,keyboard-interactive).
>>>> The patch will crash SSH :|
>>>>
>>>
>>>
>>>
>>> without looking at the patch, I think this isn't the causer of the
>>> patch at all.
>>>
>>> ciao, Marc
>>>
>>>
>>>
>> 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.
>
>
> Are you claiming that the unpatched 2.6 kernel works and the patched
> didn't? Or that 2.6 doesn't work right in general on your system
> because of configuration issues? Unless the same 2.6 kernel works
> without the patch how can you even tell what is failing?
>
Well im sorry if i caused some mess ;), but it actually seems that the
patch worked. I have no idea what when wrong the first time but
after further testing it worked. I would say that the problem was behind
the keyboard and not in the patch.
Thanx for all your replies and that you tried to help but it seems that
the patch is fine ;)
--
Outpost24 AB
David Jacoby
Research & Development
Office: +46-455-612310
Mobile: +46-455-612311
(www.outpost24.com) (dj@outpost24.com)
next prev parent reply other threads:[~2004-12-17 7:28 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 [this message]
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=41C28A76.4080905@outpost24.com \
--to=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