From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Re[2]: 'password' command in GRUB 2?
Date: Fri, 28 Aug 2009 14:37:41 +0200 [thread overview]
Message-ID: <20090828123741.GA15030@thorin> (raw)
In-Reply-To: <d7ead6de0908261032y3afb1ca2t6655303a912b5d26@mail.gmail.com>
On Wed, Aug 26, 2009 at 07:32:37PM +0200, Vladimir 'phcoder' Serbinenko wrote:
> On Wed, Aug 26, 2009 at 1:51 PM, Michal Suchanek<hramrach@centrum.cz> wrote:
> > 2009/8/25 Vladimir 'phcoder' Serbinenko <phcoder@gmail.com>:
> >>> However, that CVE is about grub leaving its passwords in memory.
> >>> Wiping memory used by grub should be fast - orders of magnitude faster
> >>> than loading the OS kernel for example.
> >> Actually this specific report is about BIOS leaving its keyboard
> >> buffer - you can find BIOS password there too. As BIOS is proprietary
> >> firmware whatever we do we can never ensure it being secure. Even the
> >
> > Even if many BIOSes leave their password there it's not reason to be as sloppy.
> >
> Let me clarify my position:
> 1) If someone submits a patch with clean (E.g. shredding grub_free,
> ensure there is no memory leak and a shredder for BIOS buffer) then I
> would recomment to merge this patch
> 2) This is a considerable amount of work and not a priority.
> 3) It's not a reason to hold the release
root's ability to read GRUB password from physical memory is already obvious
by the fact that it is stored in clear text in grub.cfg.
When we support password hashing, this should be contemplated as well.
But for now, I agree with Vladimir that this isn't a reason to hold the
release.
--
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:[~2009-08-28 12:38 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-05 17:36 'password' command in GRUB 2? Colin Watson
2009-06-05 17:55 ` Vladimir 'phcoder' Serbinenko
2009-06-05 18:17 ` Re[2]: " Julien RANC
2009-07-26 14:40 ` Felix Zielcke
2009-07-26 16:20 ` Vladimir 'phcoder' Serbinenko
2009-07-26 21:29 ` Vladimir 'phcoder' Serbinenko
2009-08-20 16:44 ` Robert Millan
2009-08-21 11:30 ` Vladimir 'phcoder' Serbinenko
2009-08-22 19:47 ` Vladimir 'phcoder' Serbinenko
2009-08-23 10:14 ` Robert Millan
2009-08-24 22:36 ` Robert Millan
2009-08-24 23:58 ` Vladimir 'phcoder' Serbinenko
2009-08-25 14:35 ` Felix Zielcke
2009-08-25 14:50 ` Vladimir 'phcoder' Serbinenko
2009-08-25 18:55 ` Michal Suchanek
2009-08-25 19:54 ` Vladimir 'phcoder' Serbinenko
2009-08-26 11:51 ` Michal Suchanek
2009-08-26 17:32 ` Vladimir 'phcoder' Serbinenko
2009-08-28 12:37 ` Robert Millan [this message]
2009-08-19 15:08 ` Robert Millan
2009-08-19 15:17 ` Vladimir 'phcoder' Serbinenko
2009-08-20 16:32 ` 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=20090828123741.GA15030@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.