All of lore.kernel.org
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: breno_silva@bandnet.com.br
Cc: linux-kernel@vger.kernel.org
Subject: Re: Exploit for the Kernel
Date: Fri, 18 Oct 2002 18:51:16 -0700 (PDT)	[thread overview]
Message-ID: <20021018.185116.128890469.davem@redhat.com> (raw)
In-Reply-To: <000d01c27710$c3a75260$cddea7c8@bsb.virtua.com.br>

   From: "Breno" <breno_silva@bandnet.com.br>
   Date: Fri, 18 Oct 2002 22:42:12 -0300

   http://online.securityfocus.com/archive/1/295855/2002-10-15/2002-10-21/1 
   
There is nothing concrete at all about said "exploit".

It looks like just a clever way to divert the victim's
attention from the real mechanism these guys are using
to root peoples boxes.

It is nearly impossible for a TCP frag handling exploit
to allow a root shell and socket to that shell to be
created.  So I think the claims are total nonsense.

  reply	other threads:[~2002-10-19  1:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-19  1:42 Exploit for the Kernel Breno
2002-10-19  1:51 ` David S. Miller [this message]
2002-10-19  2:07   ` Keith Owens
2002-10-19  2:06     ` David S. Miller
2002-10-19  6:39 ` Wolfgang Fritz
2002-10-19  8:48   ` Keith Owens

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=20021018.185116.128890469.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=breno_silva@bandnet.com.br \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.