From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] erase variable data on user unset
Date: Sun, 10 Feb 2008 22:53:25 +0100 [thread overview]
Message-ID: <20080210215325.GA8034@thorin> (raw)
In-Reply-To: <47AF6EDD.1020304@isaac.cedarswampstudios.org>
On Sun, Feb 10, 2008 at 04:38:37PM -0500, Isaac Dupree wrote:
> on second thought, if grub is going to be able to boot kernels that are
> on encrypted partitions, the password might go more places in grub
> and/or have to be retained until boot time, depending how it works...
Not until boot time, just up to the load command. I guess you mean
something like:
echo -n "Password: "
read password
lvm_somecommand $password
linux (lvm-device)/boot/linux.img
unset password
boot
Here, the lvm module would be responsible for its own copy of the password. It
does already know that sensitive information is being handled, so when
grub_lvm_fini() is called, it'll erase it.
The other copy is in the environment, so user clears it after loading linux,
because our env handler doesn't know that some variables might contain
sensitive info.
--
Robert Millan
<GPLv2> I know my rights; I want my phone call!
<DRM> What use is a phone call… if you are unable to speak?
(as seen on /.)
next prev parent reply other threads:[~2008-02-10 21:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-10 13:16 [PATCH] read --echo=[yes|no|wildcard] Robert Millan
2008-02-10 13:56 ` Isaac Dupree
2008-02-10 15:22 ` Robert Millan
2008-02-10 16:41 ` Isaac Dupree
2008-02-10 17:00 ` Robert Millan
2008-02-10 18:00 ` Isaac Dupree
2008-02-10 19:39 ` Robert Millan
2008-02-10 20:00 ` Isaac Dupree
2008-02-10 20:47 ` [PATCH] erase variable data on user unset Robert Millan
2008-02-10 21:00 ` Robert Millan
2008-02-10 21:31 ` Isaac Dupree
2008-02-10 21:38 ` Isaac Dupree
2008-02-10 21:53 ` Robert Millan [this message]
2008-02-10 20:16 ` [PATCH] read --echo=[yes|no|wildcard] Yoshinori K. Okuji
2008-02-10 20:49 ` 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=20080210215325.GA8034@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.