Grub Development Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Peter <dn.tlp@gmx.net>
To: grub-devel@gnu.org
Subject: Strong Crypto Support for GRUB2
Date: Sun, 2 Sep 2007 14:17:36 +0200	[thread overview]
Message-ID: <20070902141736.af8d1d50.dn.tlp@gmx.net> (raw)

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

Hi,

along the lines of a FeatureRequests GRUB2 Wiki entry I made earlier, I
added strong cryptography support to GRUB that allows Linux encrypted
partitions to be read. The patch is attached.

It currently features AES support, both in ECB and CBC mode with
Linux-style "plain mode" sector-based initialization vectors and
256-bit keys. The RIPEMD 160-bit hash function is also supported.

Support for encrypted devices is strongly modelled after Linux'
dm-crypt module: A device-mapper command called 'devmap' is included to
map devices or partitions onto virtual devices that transparently
decrypt data (encryption is not fully implemented yet, but should be a
breeze to add as all functions are already there). Key size mangling is
identical to that of Linux' cryptsetup command.

Cryptographic functionality is modularized and decoupled from the device
mapper so other modules can freely use it as well. Things like
encrypted serial or network connections to GRUB are conceivable, for
example.

LUKS is not supported yet, but I'm thinking about it (I don't currently
need it personally, that's why). I'd be glad for any help.

As stated in the Wiki entry, the main motivation for this is to get rid
of unencrypted boot partitions and have an encrypted kernel and initrd,
which, besides being a lot easier to maintain, also greatly enhances
security (details in the Wiki entry).

Simon

[-- Attachment #2: crypto.dif --]
[-- Type: video/dv, Size: 76580 bytes --]

             reply	other threads:[~2007-09-02 12:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-02 12:17 Simon Peter [this message]
2007-09-02 16:05 ` Strong Crypto Support for GRUB2 Robert Millan
2007-09-02 17:25   ` Simon Peter
2007-09-02 19:41     ` Robert Millan
2007-09-02 20:53       ` Simon Peter
2007-09-02 23:05         ` Robert Millan
2007-09-03 18:51           ` Simon Peter
2007-11-10 17:20             ` Marco Gerards
2007-09-03  9:42       ` Patrick Georgi
  -- strict thread matches above, loose matches on Subject: below --
2007-09-13  9:16 Simon Peter
2007-11-10 17:22 ` Marco Gerards
2008-07-20 23:49 Fw: " Simon Peter
2008-07-21 13:48 ` Colin D Bennett
2008-07-21 20:38   ` Simon Peter
2008-07-22 22:12     ` Robert Millan

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=20070902141736.af8d1d50.dn.tlp@gmx.net \
    --to=dn.tlp@gmx.net \
    --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