All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ragnar Hojland Espinosa <ragnar_hojland@eresmas.com>
To: Dan Hollis <goemon@anime.net>
Cc: David Woodhouse <dwmw2@infradead.org>,
	Christer Weinigel <wingel@hog.ctrl-c.liu.se>,
	linux-kernel@vger.kernel.org
Subject: Re: BTTV detection broken in 2.4.0-test11-pre5
Date: Mon, 20 Nov 2000 16:47:30 +0100	[thread overview]
Message-ID: <20001120164730.A176@macula.net> (raw)
In-Reply-To: <Pine.LNX.4.30.0011200115070.1076-100000@imladris.demon.co.uk> <Pine.LNX.4.30.0011191858180.18624-100000@anime.net>
In-Reply-To: <Pine.LNX.4.30.0011191858180.18624-100000@anime.net>; from Dan Hollis on Sun, Nov 19, 2000 at 07:00:41PM -0800

On Sun, Nov 19, 2000 at 07:00:41PM -0800, Dan Hollis wrote:
> On Mon, 20 Nov 2000, David Woodhouse wrote:
> > On Sun, 19 Nov 2000, Dan Hollis wrote:
> > > Writeprotect the flashbios with the motherboard jumper, and remove the
> > > cmos battery.
> > > Checkmate. :-)
> > Only if you run your kernel XIP from the flash. If you load it into RAM,
> > it's still possible for an attacker to modify it. You can load new code
> > into the kernel even if the kernel doesn't make it easy for you by having
> > CONFIG_MODULES defined.
> 
> The original assertion made was that a script kiddie could modify the
> kernel so you wouldnt be able to detect a rooted box even after a reboot.
> 
> What I posted would stop that cold, 100%. Boot from writeprotected floppy,
> writeprotect the flashbios, and remove the cmos battery.

There was some patch floating around so you could boot a new kernel without
having to reboot.  And I'm guessing you could also "box" it into a plex86
vm.

-- 
____/|  Ragnar Højland     Freedom - Linux - OpenGL      Fingerprint  94C4B
\ o.O|                                                   2F0D27DE025BE2302C
 =(_)=  "Thou shalt not follow the NULL pointer for      104B78C56 B72F0822
   U     chaos and madness await thee at its end."       hkp://keys.pgp.com

Handle via comment channels only.
-
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/

  reply	other threads:[~2000-11-20 18:21 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
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 [this message]
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=20001120164730.A176@macula.net \
    --to=ragnar_hojland@eresmas.com \
    --cc=dwmw2@infradead.org \
    --cc=goemon@anime.net \
    --cc=linux-kernel@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.