DM-Crypt Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Milan Broz <gmazyland@gmail.com>
To: Trinh Van Thanh <eyestormit@gmail.com>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] Integrate cryptsetup in bootloader
Date: Tue, 19 Nov 2013 05:56:19 +0100	[thread overview]
Message-ID: <528AEF73.8040201@gmail.com> (raw)
In-Reply-To: <CAHRe4pM3p3DooaTQXmAJz+GeJ9VPRFjeTXrusMrtef4SBzsAnw@mail.gmail.com>



On 11/19/2013 03:20 AM, Trinh Van Thanh wrote:
> Hi all,
> 
> Unencrypted boot partition is not safe for some special requirements.
> So I want to increase the secure level for full disk encryption using
> dm-crypt. Can I integrate cryptsetup in bootloader (example GRUB2) or
> is there any other solutions?

FYI GRUB2 has some LUKS support already integrated, you can try it...
It is reimplementation, just some code was copied from cryptsetup.
See e.g. Gentoo wiki
http://wiki.gentoo.org/wiki/GRUB2#Booting_from_LUKS_Physical_Volume

But I think not many people using it, initramfs with boot partition
is most common.

Milan

      parent reply	other threads:[~2013-11-19  4:56 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-19  2:20 [dm-crypt] Integrate cryptsetup in bootloader Trinh Van Thanh
2013-11-19  2:52 ` Arno Wagner
2013-11-19  3:42   ` Ralf Ramsauer
2013-11-19  4:20     ` Arno Wagner
2013-11-19 13:38       ` Ralf Ramsauer
2013-11-20 15:34         ` Arno Wagner
2013-11-27  2:16           ` Trinh Van Thanh
2013-11-27 13:45             ` Ralf Ramsauer
2013-11-19 23:28       ` Sven Eschenberg
2013-11-20  0:28         ` Ralf Ramsauer
2013-11-20  1:13           ` Sven Eschenberg
2013-11-20  9:24             ` Alex Elsayed
2013-11-19  3:27 ` Christoph Anton Mitterer
2013-11-20  9:09   ` Alex Elsayed
2013-11-20  9:14     ` Alex Elsayed
2013-11-19  4:56 ` Milan Broz [this message]

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=528AEF73.8040201@gmail.com \
    --to=gmazyland@gmail.com \
    --cc=dm-crypt@saout.de \
    --cc=eyestormit@gmail.com \
    /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