From: remco@rc6.org (Remco B. Brink)
To: <kernel@ddx.a2000.nu>
Cc: <linux-kernel@vger.kernel.org>, Enforcer <enforcer@ddx.a2000.nu>
Subject: Re: Strange errors in /var/log/messages
Date: 02 Jul 2001 18:11:15 +0200 [thread overview]
Message-ID: <m3wv5rl3a4.fsf@solbors.no> (raw)
In-Reply-To: <Pine.LNX.4.30.0107021800410.5490-100000@ddx.a2000.nu>
<kernel@ddx.a2000.nu> writes:
> Hi!
>
> I'm running RedHat 7.0 with all official RH patches applied. The kernel I
> currently run fow a few days is 2.2.19-7.0.8
> I run the pre-compiled kernel of RH. Suddenly I the following messages:
<snip error messages>
> This continued for about half an hour. Then it stopped. What's going on
> here??
Here you have two options:
You are either under attack by someone who's trying to exploit your
LPRng (someone's trying to use LPR's logging function to get a shell).
This is the LPRng string format _syslog bug that theoretically could
allow root access. For more info check http://www.securityfocus.com/vdb/bottom.html?vid=1712
The other option is that you're under rpc.statd attack at the moment.
In either case, make sure you upgraded to the latest patch versions
and subscribe to BugTraq and the Security Focus Incidents mailinglist :)
regards,
Remco
--
Remco B. Brink - SOL Børs A/S systemsdeveloper - http://www.norge-invest.no
Personal site at http://rc6.org - PGP/GnuPG key at http://rc6.org/rbb.pgp
"What you end up with, after running an operating system concept through
these many marketing coffee filters, is something not unlike plain hot
water."
(By Matt Welsh)
next prev parent reply other threads:[~2001-07-02 16:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-02 16:05 kernel
2001-07-02 16:11 ` Remco B. Brink [this message]
2001-07-02 16:16 ` Alan Cox
2001-07-02 17:42 ` Guest section DW
2001-07-02 19:51 ` kernel
2001-07-03 7:45 ` David Weinehall
2001-07-02 17:00 ` Richard B. Johnson
2001-07-02 18:23 ` [OT] " Ville Herva
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=m3wv5rl3a4.fsf@solbors.no \
--to=remco@rc6.org \
--cc=enforcer@ddx.a2000.nu \
--cc=kernel@ddx.a2000.nu \
--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®