grub-devel.gnu.org archive mirror
 help / color / mirror / Atom feed
From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: Behaviour if GRUB_ENABLE_CRYPTODISK is unset?
Date: Sat, 07 Dec 2013 14:49:45 +0100	[thread overview]
Message-ID: <52A32779.9030604@gmail.com> (raw)
In-Reply-To: <20131207132726.GA28299@riva.ucam.org>

[-- Attachment #1: Type: text/plain, Size: 597 bytes --]

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.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 291 bytes --]

  reply	other threads:[~2013-12-07 13:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-07 13:27 Behaviour if GRUB_ENABLE_CRYPTODISK is unset? Colin Watson
2013-12-07 13:49 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2013-12-07 14:00   ` Colin Watson
2013-12-07 23:42     ` Chris Murphy
2013-12-07 23:54       ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-12-09 11:37       ` Colin Watson
2013-12-10  0:17         ` Chris Murphy
2013-12-07 13:54 ` Andrey Borzenkov

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=52A32779.9030604@gmail.com \
    --to=phcoder@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).