From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Luks inclusion (was Re: GRUB 1.99~rc2 released)
Date: Sat, 23 Apr 2011 00:30:21 +0200 [thread overview]
Message-ID: <4DB2017D.7080209@gmail.com> (raw)
In-Reply-To: <BANLkTinF=QJconqZu8SaxZzOzCRCFuSacQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1333 bytes --]
On 21.04.2011 17:29, Craig Sparks wrote:
>
> When is luks going to be added so we can encrypt the boot partition also?
>
I've cleaned the patch (took a lot of time), not because I believe it's
a useful feature but since it has become an often requested one.
The branch is available at
http://bzr.savannah.gnu.org/r/grub/branches/luks/ .
You need to set GRUB_LUKS_ENABLE=y. Beware that:
a) Crypto in GRUB is much less performant than in kernel due to
inavailability of many accelerated instructions. So prepare for key
recovery taking considerable time or decrease key strengthening.
b) You'll need to enter passphrase twice. Once for GRUB, once for OS.
c) Encrypting doesn't guarantee integrity. Your /boot can be tempered
with even if it's encrypted and GRUB has no way of finding it out.
Encryption is about secrecy and /boot doesn't contain anything secret.
d) core is unencrypted (since BIOS has no encryption support)
e) core needs a much bigger embedding zone
f) no writing to luks as of now.
But even regardless of all that criticism which puts this as
low-priority, I'm fed up with feature requests and since unless it's
activated manually LUKS in GRUB doesn't kick in, I've done the cleanup.
Now you do the tests and report the results back
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 294 bytes --]
next prev parent reply other threads:[~2011-04-22 22:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-20 14:37 GRUB 1.99~rc2 released Vladimir 'φ-coder/phcoder' Serbinenko
2011-04-21 7:48 ` Treutwein Bernhard
[not found] ` <BANLkTimQzFVfZ+ah=0EBm_mQWiXFcr2nwA@mail.gmail.com>
2011-04-21 15:29 ` Craig Sparks
2011-04-22 22:30 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2011-04-25 13:21 ` [RFT] LUKS and GELI (was Re: Luks inclusion) Vladimir 'φ-coder/phcoder' Serbinenko
2011-04-22 22:34 ` Keyboard layouts (was Re: GRUB 1.99~rc2 released) Vladimir 'φ-coder/phcoder' Serbinenko
2011-05-03 9:04 ` grub-mklayout - Unknown key KP_Comma (was: Keyboard layouts & previously: " Treutwein Bernhard
2011-05-03 9:19 ` grub-mklayout - Unknown key KP_Comma Vladimir 'φ-coder/phcoder' Serbinenko
2011-05-23 13:22 ` Keyboard layouts Treutwein Bernhard
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=4DB2017D.7080209@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 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.