Bug#491376: recipe for BIOS-based boot on gpt
- To: email@example.com
- Subject: Bug#491376: recipe for BIOS-based boot on gpt
- From: Robert Millan <firstname.lastname@example.org>
- Date: Mon, 4 Aug 2008 11:18:34 +0200
- Message-id: <[🔎] 20080804091834.GA1078@thorin>
- Reply-to: Robert Millan <email@example.com>, firstname.lastname@example.org
- In-reply-to: <20080727164113.GA5132@thorin>
- References: <20080719005848.9240.43333.reportbug@thorin> <email@example.com> <20080719130425.GA21080@thorin> <20080720070856.GA22769@thorin> <20080725150301.GA8217@thorin> <20080727115940.GA9709@thorin> <20080727164113.GA5132@thorin>
So what do we do about this? I wouldn't want to miss the deadline...
On Sun, Jul 27, 2008 at 06:41:13PM +0200, Robert Millan wrote:
> On Sun, Jul 27, 2008 at 01:59:40PM +0200, Robert Millan wrote:
> > on a system where core.img was embedded, nothing will happen. OTOH if you do
> > the same on a system where core.img was referenced via blocklists, boot will
> > start crashing as soon as the (now free) blocks that held the old core.img
> > are overwritten.
> Ah, and in a worst-case scenario someone could even try to exploit it to
> run privileged code, by creating a carefuly crafted huge file.
> Robert Millan
> <GPLv2> I know my rights; I want my phone call!
> <DRM> What good is a phone call… if you are unable to speak?
> (as seen on /.)
> To UNSUBSCRIBE, email to debian-boot-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact firstname.lastname@example.org
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."