mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Richard B. Johnson" <root@chaos.analogic.com>
To: Charles Cazabon <linux@discworld.dyndns.org>
Cc: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: FATAL: Kernel too old
Date: Fri, 6 Feb 2004 17:20:10 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.53.0402061718030.917@chaos> (raw)
In-Reply-To: <20040206152943.B26348@discworld.dyndns.org>

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!


Cheers,
Dick Johnson
Penguin : Linux version 2.4.24 on an i686 machine (797.90 BogoMips).
            Note 96.31% of all statistics are fiction.



  parent reply	other threads:[~2004-02-06 22:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-06 21:16 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 [this message]
2004-02-06 23:22     ` Bryan Andersen
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=Pine.LNX.4.53.0402061718030.917@chaos \
    --to=root@chaos.analogic.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@discworld.dyndns.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®