From: Andrei Borzenkov <arvidjaar@gmail.com>
To: Barry Jackson <zen25000@zen.co.uk>
Cc: grub-devel@gnu.org
Subject: Re: Query about GRUB_ENABLE_CRYPTODISK
Date: Wed, 10 Dec 2014 06:25:58 +0300 [thread overview]
Message-ID: <20141210062558.15524434@opensuse.site> (raw)
In-Reply-To: <54878575.6090501@zen.co.uk>
В Tue, 09 Dec 2014 23:27:49 +0000
Barry Jackson <zen25000@zen.co.uk> пишет:
> On 09/12/14 22:36, Barry Jackson wrote:
> > On 09/12/14 18:27, Andrei Borzenkov wrote:
> >> В Tue, 09 Dec 2014 12:35:20 +0000
> >> Barry Jackson <zen25000@zen.co.uk> пишет:
> >>
> >>> Hello,
> >>> In Mageia it has been proposed that GRUB_ENABLE_CRYPTODISK=y be made the
> >>> default setting in /etc/default/grub for all installations, whether they
> >>> use encryption or not.
> >>
> >> The discussion happens every now and then.
> >>
> >> http://lists.gnu.org/archive/html/grub-devel/2013-12/msg00112.html
> >
> > OK, thanks for the link.
> >
> > In the case of Mageia the default installation puts everything required
> > by grub under /boot, so AFAICT this should not cause a problem.
>
> ... but it does.
>
> I found time to do some testing, and adding it to the config on a system
> with no encryption at all causes an error message:
> error: device name required.
>
> this seems to be triggered by this line which grub-mkconfig adds to
> grub.cfg:
>
> cryptomount -u
>
Does patch below help?
From: Andrei Borzenkov <arvidjaar@gmail.com>
Subject: [PATCH] do not emit cryptomount without crypto UUID
---
util/grub-mkconfig_lib.in | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/util/grub-mkconfig_lib.in b/util/grub-mkconfig_lib.in
index 29ef865..60b31ca 100644
--- a/util/grub-mkconfig_lib.in
+++ b/util/grub-mkconfig_lib.in
@@ -145,7 +145,7 @@ prepare_grub_to_access_device ()
done
if [ x$GRUB_ENABLE_CRYPTODISK = xy ]; then
- for uuid in "`"${grub_probe}" --device $@ --target=cryptodisk_uuid`"; do
+ for uuid in `"${grub_probe}" --device $@ --target=cryptodisk_uuid`; do
echo "cryptomount -u $uuid"
done
fi
--
tg: (bac5d1a..) u/mkconfig-cryptomount (depends on: master)
next prev parent reply other threads:[~2014-12-10 3:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-09 12:35 Query about GRUB_ENABLE_CRYPTODISK Barry Jackson
2014-12-09 18:27 ` Andrei Borzenkov
2014-12-09 22:36 ` Barry Jackson
2014-12-09 23:27 ` Barry Jackson
2014-12-10 3:25 ` Andrei Borzenkov [this message]
2014-12-10 20:48 ` Barry Jackson
2015-03-27 15:28 ` Vladimir 'φ-coder/phcoder' Serbinenko
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=20141210062558.15524434@opensuse.site \
--to=arvidjaar@gmail.com \
--cc=grub-devel@gnu.org \
--cc=zen25000@zen.co.uk \
/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).