From: Isaac Dupree <id@isaac.cedarswampstudios.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] read --echo=[yes|no|wildcard]
Date: Sun, 10 Feb 2008 13:00:50 -0500 [thread overview]
Message-ID: <47AF3BD2.6060305@isaac.cedarswampstudios.org> (raw)
In-Reply-To: <20080210170026.GA12941@thorin>
Robert Millan wrote:
> I think that it'd be better to just erase all our environment in
> grub_machine_fini() or a similar routine, than to give read specific knowledge
> that its data needs this kind of special protection. Besides, it wouldn't be
> that simple since the data is controlled by the user via grub.cfg, not directly
> by GRUB.
I wonder if this erasing would take any significant amount of time (in
which case there would be a reason not to implement that to happen all
the time)
> Anyway, untill we support hashing this doesn't provide any additional security,
> since you can get the same from grub.cfg ;-)
fairly true, assuming nothing weird happens like grub.cfg being
thoroughly deleted in the meantime :-)
anyway if a hash is used that takes (by design) around one second on the
machine (e.g. sha256 repeated thousands? millions? of times), then I
suppose the time taken to erase the memory used by GRUB would be trivial
in comparison, assuming(rightly or wrongly) a good implementation...
-Isaac
next prev parent reply other threads:[~2008-02-10 18:01 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 [this message]
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
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=47AF3BD2.6060305@isaac.cedarswampstudios.org \
--to=id@isaac.cedarswampstudios.org \
--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.