From: John Lane <grub@jelmail.com>
To: grub-devel@gnu.org
Subject: Re: Cryptomount enhancements - revised
Date: Tue, 28 Jul 2015 19:51:13 +0100 [thread overview]
Message-ID: <55B7CF21.3080808@jelmail.com> (raw)
In-Reply-To: <1435588260-29456-1-git-send-email-grub@jelmail.com>
On 29/06/15 15:30, John Lane wrote:
> These patches provide extensions to the "cryptomount" command. There are five patches
>
> [PATCH 1/5] Cryptomount support LUKS detached header
> Support LUKS detached headers so that the header can be separated from the data payload, e.g. by storing on external removable media such as a USB key.
>
> [PATCH 2/5] Cryptomount support key files
> Support key files so that passphrase entry can be suppressed. The passphrase can be stored in a "key file" that can be stored, for example, on external removable media such as a USB key.
>
> [PATCH 3/5] cryptomount luks allow multiple passphrase attempts
> Allow a second attempt to enter a passphrase. If unlocking fails on the first attempt then the user is presented with the passphrase entry prompt again. If a key file is given that does not unlock the device then the user is given the opportunity to enter a passphrase.
>
> [PATCH 4/5] Cryptomount support plain dm-crypt
> Support plain dm-crypt mode. Allow plain volumes to be opened. This is largely a re-factoring of exisitng code to allow the crypto routines be used independently of LUKS.
>
> [PATCH 5/5] Cryptomount support for hyphens in UUID
> Support for hyphens in UUID. The "-u" option of cryptomount accepts a UUID. This option allows that to be delimited with hyphens so that the same format can be given to Grub as is passed to the Linux kernel boot options.
>
>
> This is a revised patch set following feedback from patches sent on 16/6/15.
>
> grub-core/disk/cryptodisk.c | 382 ++++++++++++++++++++++++++++++++++++++++++++++++++--
> grub-core/disk/geli.c | 9 +-
> grub-core/disk/luks.c | 508 +++++++++++++++++++++++++--------------------------------------------
> include/grub/cryptodisk.h | 18 ++-
> 4 files changed, 581 insertions(+), 336 deletions(-)
>
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel
>
Just wondering if there's any feedback on these patches... It's been a
while since I posted them.
next prev parent reply other threads:[~2015-07-28 18:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-29 14:30 Cryptomount enhancements - revised John Lane
2015-06-29 14:30 ` [PATCH 1/5] Cryptomount support LUKS detached header John Lane
2015-06-29 14:30 ` [PATCH 2/5] Cryptomount support key files John Lane
2015-06-29 14:30 ` [PATCH 3/5] cryptomount luks allow multiple passphrase attempts John Lane
2015-06-29 14:56 ` John Lane
2015-06-29 14:30 ` [PATCH 4/5] Cryptomount support plain dm-crypt John Lane
2016-02-12 15:19 ` Vladimir 'φ-coder/phcoder' Serbinenko
2015-06-29 14:31 ` [PATCH 5/5] Cryptomount support for hyphens in UUID John Lane
2015-06-29 14:52 ` John Lane
2015-07-29 3:08 ` Andrei Borzenkov
2015-07-29 6:51 ` John Lane
2015-07-29 16:51 ` Andrei Borzenkov
2015-07-29 18:53 ` John Lane
2015-07-28 18:51 ` John Lane [this message]
2015-07-28 21:38 ` Cryptomount enhancements - revised Vladimir 'phcoder' Serbinenko
2015-07-29 6:48 ` John Lane
2015-07-29 17:21 ` Andrei Borzenkov
2015-08-01 16:22 ` John Lane
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=55B7CF21.3080808@jelmail.com \
--to=grub@jelmail.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.