From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [RFC] Boot parameters and geometrical stability
Date: Thu, 4 Sep 2008 21:37:14 +0200 [thread overview]
Message-ID: <20080904193714.GE9133@thorin> (raw)
In-Reply-To: <48BECE1A.1070406@nic.fi>
On Wed, Sep 03, 2008 at 08:49:14PM +0300, Vesa Jääskeläinen wrote:
>
> Possibilites are there, but basically they are limited to something like:
>
> (ata0) (pci-X-Y-Z:ata0) (usb-X-Y:scsi0) (pci-X-Y-Z:scsi0)
I think this is overkill, and doesn't really address the root of the problem.
The real security problem here is whether the executable code you're loading is
trusted, NOT where you load the code from.
When you use crypto checksums, if you get a match why would you care if you're
loading from (some-safe-disk) or from (evil-place)? It's the same data!
--
Robert Millan
The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
how) you may access your data; but nobody's threatening your freedom: we
still allow you to remove your data and not access it at all."
next prev parent reply other threads:[~2008-09-04 19:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-03 9:50 [RFC] Boot parameters and geometrical stability phcoder
2008-09-03 10:36 ` Robert Millan
2008-09-03 12:31 ` phcoder
2008-09-03 16:51 ` Vesa Jääskeläinen
2008-09-03 17:17 ` phcoder
2008-09-03 17:49 ` Vesa Jääskeläinen
2008-09-03 18:36 ` phcoder
2008-09-03 19:07 ` Vesa Jääskeläinen
2008-09-03 19:23 ` phcoder
2008-09-04 19:37 ` Robert Millan [this message]
2008-09-04 21:40 ` phcoder
2008-09-05 9:58 ` Robert Millan
2008-09-04 19:33 ` Robert Millan
2008-09-04 21:37 ` phcoder
2008-09-05 10:05 ` Robert Millan
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=20080904193714.GE9133@thorin \
--to=rmh@aybabtu.com \
--cc=grub-devel@gnu.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 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.