From: Jure Pecar <pegasus@nerv.eu.org>
To: linux-kernel@vger.kernel.org
Subject: some new remote kernel exploit?
Date: Tue, 8 Apr 2003 03:33:15 +0200 [thread overview]
Message-ID: <20030408033315.42f407ec.pegasus@nerv.eu.org> (raw)
Hi all,
Please see my post to the redhat list at
https://listman.redhat.com/pipermail/valhalla-list/2003-April/025830.html
I'm getting more and more affraid ... since now the the third box was
targeted and there were more attempts at 22:00-22:47 localtime (gmt+1).
rpm -Va shows nothing suspicious, so i hope these are still only attempts.
I have put the ksymoops from the logs at http://nerv.eu.org/oopsen/ if you
want to see them all.
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.
Please cc me on replies. Thanks.
--
Jure Pecar
next reply other threads:[~2003-04-08 1:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-08 1:33 Jure Pecar [this message]
2003-04-08 11:59 ` Alan Cox
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=20030408033315.42f407ec.pegasus@nerv.eu.org \
--to=pegasus@nerv.eu.org \
--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
all inboxes | Powered by JetHome®