From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Jure Pecar <pegasus@nerv.eu.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: some new remote kernel exploit?
Date: 08 Apr 2003 12:59:22 +0100 [thread overview]
Message-ID: <1049803162.8113.18.camel@dhcp22.swansea.linux.org.uk> (raw)
In-Reply-To: <20030408033315.42f407ec.pegasus@nerv.eu.org>
On Maw, 2003-04-08 at 02:33, Jure Pecar wrote:
> I'm pretty much without ideas how to track this down ... expect to sit at
> the computer for the next 24h and be ready to start dumping traffic at the
> moment it starts again.
If its an attack, then it would imply someone patched the kernel image
syscall table stuff or around there and got it wrong, perhaps precisely
because your kernels are custom.
next prev parent reply other threads:[~2003-04-08 12:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-08 1:33 Jure Pecar
2003-04-08 11:59 ` Alan Cox [this message]
2003-04-28 23:34 ` SIGRTMIN, F_SETOWN(-getpgrp()) and threads Lamont Granquist
2003-04-29 12:08 ` Alex Riesen
2003-04-29 20:14 ` Lamont Granquist
2003-04-30 9:15 ` Alex Riesen
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=1049803162.8113.18.camel@dhcp22.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=pegasus@nerv.eu.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
all inboxes | Powered by JetHome®