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
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...
___
Grub-devel mailing list
Grub-devel@gn
Robert Millan wrote:
On Sun, Feb 10, 2008 at 03:00:31PM -0500, Isaac Dupree wrote:
Robert Millan wrote:
On Sun, Feb 10, 2008 at 01:00:50PM -0500, Isaac Dupree wrote:
anyway if a hash is used that takes (by design) around one second on the
machine (e.g. sha256 repeated thousands? millions? of t
On Sun, Feb 10, 2008 at 09:47:38PM +0100, Robert Millan wrote:
>
> This should address your concern. As to why I propose to put this in unset
> command rather than kernel, since GRUB itself doesn't have any mechanisms
> where a variable would contain sensible information, I think it's better to
>
On Sun, Feb 10, 2008 at 03:00:31PM -0500, Isaac Dupree wrote:
> Robert Millan wrote:
> >On Sun, Feb 10, 2008 at 01:00:50PM -0500, Isaac Dupree wrote:
> >>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
