From: Jonas Diemer <diemer@gmx.de>
To: Vernon Mauery <vmauery@gmail.com>
Subject: Re: security issue: hard disk lock
Date: Tue, 5 Apr 2005 19:10:30 +0200
User-Agent: KMail/1.8
Cc: Horst von Brand <vonbrand@inf.utfsm.cl>, linux-kernel@vger.kernel.org
References: <200504041832.j34IW6PO030096@laptop11.inf.utfsm.cl> <4252B1A9.3040005@gmail.com>
In-Reply-To: <4252B1A9.3040005@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 8BIT
Content-Disposition: inline
Message-Id: <200504051910.30562.diemer@gmx.de>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 930
Lines: 20

Am Dienstag 05. April 2005 17:41 schrieb Vernon Mauery:
> ?This makes sense because a particularly malicious
> place to put something like this is a worm that attaches to your boot
> loader. ?Then, even doing it in the kernel at boot time is too late.

I understand... Didn't know that worms could attach to the bootloader :-) 
Well, then even fixing this in the bootloader would be too late, if the worm 
could simply replace the bootloader. I guess it's not a kernel-issue then and 
should really be addressed in the boot-up sequence (as long as BIOS vendors 
fail to fix it), be it with or without initrd.

regards,
Jonas

PS: Still not in list, so please CC me on eventual replies.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/