From: Bryan Andersen <bryan@nerdvest.com>
To: root@chaos.analogic.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: FATAL: Kernel too old
Date: Fri, 06 Feb 2004 17:22:53 -0600 [thread overview]
Message-ID: <402421CD.1030605@nerdvest.com> (raw)
In-Reply-To: <Pine.LNX.4.53.0402061718030.917@chaos>
Richard B. Johnson wrote:
> On Fri, 6 Feb 2004, Charles Cazabon wrote:
>
>
>>Richard B. Johnson <root@chaos.analogic.com> wrote:
>>
>>>Script started on Fri Feb 6 15:44:32 2004
>>># rlogin -l johnson quark
>>>ATAL: kernel too old
>>># rlogin -l johnson quark
>>>ATAL: kernel too old
>>
>>I saw something similar at a customer's site, when someone rooted the box and
>>replaced the default login shell with a rootkitted/backdoored one in a newer
>>executable format not supported by the old kernel.
>>
>>
>>>I crashed it and it rebooted fine, little fsck activity, with
>>>nothing in any logs that shows there was any problem whatsoever.
>>
>>Did the problem go away with a reboot?
>
> Sure. And if you can 'root' that machine, you are really
> good! It isn't even visible to most of the company internally!
You never know what your fellow employees will do... Where there is a
will there is a way.
If you don't think it got rooted, what did you or other employees do
recently on that machine that would cause software to be changed? Did
anybody do any upgrades? Unless you can confirm an alternate
explanation then I'd assume it was rooted. If the machine was upgraded
by downloading from the net, was the site you downloaded from secure?
Just because a machine is behind many fire walls doesn't mean that it
can't be rooted.
- Bryan
next prev parent reply other threads:[~2004-02-06 23:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-06 21:16 FATAL: Kernel too old Richard B. Johnson
2004-02-06 21:29 ` Charles Cazabon
2004-02-06 21:52 ` Frédéric L. W. Meunier
2004-02-06 22:20 ` Richard B. Johnson
2004-02-06 23:22 ` Bryan Andersen [this message]
2004-02-07 6:27 ` Karl Tatgenhorst
2004-02-07 7:41 ` Andrew Walrond
2004-02-07 14:00 ` Frédéric L. W. Meunier
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=402421CD.1030605@nerdvest.com \
--to=bryan@nerdvest.com \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.com \
/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