From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from list by lists.gnu.org with archive (Exim 4.71) id 1ZKLAl-0005Hv-3w for mharc-grub-devel@gnu.org; Wed, 29 Jul 2015 02:49:03 -0400 Received: from eggs.gnu.org ([2001:4830:134:3::10]:49562) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZKLAi-0005F5-05 for grub-devel@gnu.org; Wed, 29 Jul 2015 02:49:00 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZKLAe-0000ZD-Lw for grub-devel@gnu.org; Wed, 29 Jul 2015 02:48:59 -0400 Received: from johnlane.plus.com ([212.159.104.145]:63269 helo=sodium.amajohn.co.uk) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZKLAe-0000Yp-F1 for grub-devel@gnu.org; Wed, 29 Jul 2015 02:48:56 -0400 Received: by sodium.amajohn.co.uk (Postfix, from userid 1000) id A0E646B; Wed, 29 Jul 2015 07:48:45 +0100 (BST) Received: from [10.0.200.1] (hydrogen.amajohn.co.uk [10.0.200.1]) by sodium.amajohn.co.uk (Postfix) with ESMTPSA id 40D475A for ; Wed, 29 Jul 2015 07:48:44 +0100 (BST) Message-ID: <55B87749.6090406@jelmail.com> Date: Wed, 29 Jul 2015 07:48:41 +0100 From: John Lane User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.2 MIME-Version: 1.0 To: grub-devel@gnu.org Subject: Re: Cryptomount enhancements - revised References: <1435588260-29456-1-git-send-email-grub@jelmail.com> <55B7CF21.3080808@jelmail.com> In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable X-Outbound-Checked: Yes X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 212.159.104.145 X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: The development of GNU GRUB List-Id: The development of GNU GRUB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Jul 2015 06:49:00 -0000 On 28/07/15 22:38, Vladimir 'phcoder' Serbinenko wrote: > > Other than 3 and 5 they require difficult configuration. Mapping > devices in GRUB isn't trivial. Those features are difficult to > autoconfigure. Consider "plain" mode: how will you find which disk is > yours when you have 5 disks all looking as random data? > > I don't see what's difficult about providing a LUKs header and key but I am aware of the issue re device identification in plain mode. However, if one has a use-case for these crypto routines then I think that would be a valid use-case for manually configuring grub.cfg if it's beyond what autoconfiguration supports. If an end user wants to make the choice then why deny him, just because it may be difficult to autoconfigure ? There does seem to be interest in this functionality. Surely auto-configuration would't be a bar to supporting this? I don't think I am the only one who thinks these features are useful... Regarding device identification, I had some thoughts on that and was willing to try implementing something. However I wanted to put this patch-set to bed before starting on something else.