public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ben Ford <ben@kalifornia.com>
To: Alexander Viro <viro@math.psu.edu>
Cc: Christer Weinigel <wingel@hog.ctrl-c.liu.se>,
	goemon@anime.net, linux-kernel@vger.kernel.org
Subject: Re: BTTV detection broken in 2.4.0-test11-pre5
Date: Sun, 19 Nov 2000 13:08:40 -0800	[thread overview]
Message-ID: <3A184158.4C818741@kalifornia.com> (raw)
In-Reply-To: <Pine.GSO.4.21.0011191036370.24634-100000@weyl.math.psu.edu>

Alexander Viro wrote:

> On Sun, 19 Nov 2000, Christer Weinigel wrote:
>
> > In article <Pine.LNX.4.30.0011190710440.13087-100000@anime.net> you write:
> > >On Sun, 19 Nov 2000, Alexander Viro wrote:
> > >> On Sun, 19 Nov 2000, David Lang wrote:
> > >> > there is a rootkit kernel module out there that, if loaded onto your
> > >> > system, can make it almost impossible to detect that your system has been
> > >> > compramised. with module support disabled this isn't possible.
> > >> Yes, it is. Easily. If you've got root you can modify the kernel image and
> > >> reboot the bloody thing. And no, marking it immutable will not help. Open
> > >> the raw device and modify relevant blocks.
> > >
> > >Kernel on writeprotected floppy disk...
>
> Cute. And when (not if) we get hit by new bug in the net/*/* you will drive
> to the location of said router to upgrade the thing.
>

No, I mail the customer a new operating CD.

-b


>
> > So change the CMOS-settings so that the BIOS changes the boot order
> > from A, C, CD-ROM to C first instead.  *grin*  How long do you want
> > to keep playing Tic-Tac-Toe?
>
> Now, _that_ can be taken care of (custom boot code burnt into the thing)
>
> > Of course, using capabilities and totally disabling access to the raw
> > disk devices and to any I/O ports might be the solution, provided that
> > there are no bugs or thinkos in the capabilities code.
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> Please read the FAQ at http://www.tux.org/lkml/

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  parent reply	other threads:[~2000-11-19 21:39 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-17  0:31 BTTV detection broken in 2.4.0-test11-pre5 Werner Almesberger
2000-11-17 20:08 ` Gerd Knorr
2000-11-18 13:14   ` Werner Almesberger
2000-11-19  8:24     ` Gerd Knorr
2000-11-19 10:46       ` David Ford
2000-11-19 12:56         ` Gerd Knorr
2000-11-19 13:49           ` Keith Owens
2000-11-19 19:03             ` Gerd Knorr
2000-11-19 21:45               ` Keith Owens
2000-11-19 15:16           ` David Lang
2000-11-19 14:49             ` Alexander Viro
2000-11-19 15:11               ` Dan Hollis
2000-11-19 15:08                 ` Christer Weinigel
2000-11-19 15:45                   ` Alexander Viro
2000-11-19 15:54                     ` Dan Hollis
2000-11-19 21:08                     ` Ben Ford [this message]
2000-11-19 15:50                   ` Dan Hollis
2000-11-19 16:53                     ` Alan Cox
2000-11-19 20:53                       ` Rogier Wolff
2000-11-20  3:22                         ` Dan Hollis
2000-11-20  1:16                     ` David Woodhouse
2000-11-20  3:00                       ` Dan Hollis
2000-11-20 15:47                         ` Ragnar Hojland Espinosa
2000-11-19 16:21                   ` David Ford
2000-11-19 21:06                   ` Ben Ford
2000-11-19 14:49             ` Keith Owens
2000-11-19 17:36             ` Gerd Knorr
2000-11-19 16:02           ` David Ford
2000-11-20 10:22           ` [PATCH] " Richard Guenther
2000-11-20  2:14       ` [PATCH] bttv_card & bttv_radio (was Re: BTTV detection broken in 2.4.0-test11-pre5) Werner Almesberger
  -- strict thread matches above, loose matches on Subject: below --
2000-11-20  4:39 BTTV detection broken in 2.4.0-test11-pre5 Wayne.Brown

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=3A184158.4C818741@kalifornia.com \
    --to=ben@kalifornia.com \
    --cc=goemon@anime.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@math.psu.edu \
    --cc=wingel@hog.ctrl-c.liu.se \
    /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