[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Behaviour if GRUB_ENABLE_CRYPTODISK is unset?
From: |
Colin Watson |
Subject: |
Re: Behaviour if GRUB_ENABLE_CRYPTODISK is unset? |
Date: |
Sat, 7 Dec 2013 14:00:58 +0000 |
User-agent: |
Mutt/1.5.21 (2010-09-15) |
On Sat, Dec 07, 2013 at 02:49:45PM +0100, Vladimir 'φ-coder/phcoder' Serbinenko
wrote:
> On 07.12.2013 14:27, Colin Watson wrote:
> > I've never totally understood why GRUB_ENABLE_CRYPTODISK is optional to
> > begin with; it seems like a bit of a "do you want things to work? [y/N]"
> > option to me. My preferred approach would be to delete the option.
>
> Cryptodisk support is allowed to ask user for password which is not
> possible for unattended systems.
> E.g. in old config GRUB was looking for unifont under /usr/share. If you
> make cryptodisk default a server doing this would stop in password
> prompt rather than skipping unifont and going to text mode and
> continuing booting.
OK. I get that we don't necessarily want to be noisy if it's just for
something optional. But if somebody's /boot is on LUKS, it would be
nice to tell them how to enable support for that rather than just having
grub-mkconfig fail, right? I think grub-install already gives specific
instructions, so we could do that in grub-mkconfig too.
--
Colin Watson address@hidden
Re: Behaviour if GRUB_ENABLE_CRYPTODISK is unset?, Andrey Borzenkov, 2013/12/07