From: Erik Bourget <erik@midmaine.com>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: linux-kernel@vger.kernel.org, <netfilter@lists.netfilter.org>
Subject: Re: Three kernel Oops/panic/BUG ksymoopses (kernel BUG at buffer.c:539)
Date: Sat, 03 Jan 2004 16:50:33 -0500 [thread overview]
Message-ID: <87ekugzopi.fsf@midmaine.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0401031352040.2301-100000@poirot.grange> (Guennadi Liakhovetski's message of "Sat, 3 Jan 2004 13:54:27 +0100 (CET)")
Guennadi Liakhovetski <g.liakhovetski@gmx.de> writes:
> On Fri, 2 Jan 2004, Erik Bourget wrote:
>
>> I had a very bizarre situation where four boxes in the same rack all
>> simultaneously (within 30 minutes) hard-locked with Oops messages. The
>> boxes
>
> An obvious idea - after reading an article about a break-in into Debian
> and others' boxes - sure you weren't cracked?
Yeah, that was a concern and I'm relatively sure that's not the case because
*) chkrootkit says so (mod some hidden processes that are reported by a bug in
chkrootkit according to Google)
*) The crashy boxes were all installed with 2.4.23, not upgraded, so the big
Debian vulnerability didn't exist
*) The only open ports to the outside world are running SMTP and POP3 as
non-root no-shell accounts, and it's running qmail which seems simple and
safe enough.
- Erik Bourget
next prev parent reply other threads:[~2004-01-03 21:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-02 23:31 Three kernel Oops/panic/BUG ksymoopses (kernel BUG at buffer.c:539) Erik Bourget
2004-01-03 12:54 ` Guennadi Liakhovetski
2004-01-03 21:50 ` Erik Bourget [this message]
2004-03-29 15:40 ` Guennadi Liakhovetski
-- strict thread matches above, loose matches on Subject: below --
2004-03-29 15:39 Erik Bourget
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=87ekugzopi.fsf@midmaine.com \
--to=erik@midmaine.com \
--cc=g.liakhovetski@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netfilter@lists.netfilter.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