From: Jeff Garzik <jeff@garzik.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Kyle McMartin <kyle@canonical.com>,
linux-ide@vger.kernel.org, mjg59@ubuntu.com
Subject: Re: [RFT] libata hpa support
Date: Wed, 21 Mar 2007 14:03:47 -0400 [thread overview]
Message-ID: <46017383.2000107@garzik.org> (raw)
In-Reply-To: <20070321185024.31673dd3@lxorguk.ukuu.org.uk>
Alan Cox wrote:
>> That reminds me, there have been suggestions in the past that we should
>> do a security freeze after probing and configuring.
>
> And as has been observed previously from a security perspective there is
> no point.
>
> Break into box
> security freeze - annoying
> Patch boot block to load my disk destroyer
> Reboot
>
> You need to the security freeze in the firmware at boot, or it is the
> same whether you do it in kernel or in the initrd or early boot, except
> that its pagable code, its configurable and its easier to work with when
> it is in user space.
>
> Paranoid people get PCI boot roms that lock their disks.
Certainly.
But I argue that doing it late is better than not doing it at all.
Jeff
next prev parent reply other threads:[~2007-03-21 18:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-23 17:06 [RFT] libata hpa support Kyle McMartin
2007-02-23 18:19 ` Alan
2007-02-23 18:23 ` Colin Watson
2007-02-24 18:00 ` Kyle McMartin
2007-02-25 0:09 ` Alan
2007-02-24 23:17 ` Jeff Garzik
2007-03-05 3:47 ` Tejun Heo
2007-03-21 13:01 ` Kyle McMartin
2007-03-21 18:34 ` Alan Cox
2007-03-21 17:40 ` Matthew Garrett
2007-03-21 18:51 ` Alan Cox
2007-03-21 17:58 ` Matthew Garrett
2007-03-21 17:41 ` Jeff Garzik
2007-03-21 18:50 ` Alan Cox
2007-03-21 18:03 ` Jeff Garzik [this message]
2007-03-21 19:17 ` Alan Cox
2007-03-21 18:16 ` Jeff Garzik
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=46017383.2000107@garzik.org \
--to=jeff@garzik.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=kyle@canonical.com \
--cc=linux-ide@vger.kernel.org \
--cc=mjg59@ubuntu.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;
as well as URLs for NNTP newsgroup(s).