grub-devel.gnu.org archive mirror
 help / color / mirror / Atom feed
From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: grub-devel@gnu.org
Subject: Re: Keyfile Support for GRUBs LUKS
Date: Fri, 22 Nov 2013 04:01:21 +0100	[thread overview]
Message-ID: <528EC901.8000704@gmail.com> (raw)
In-Reply-To: <528E6058.9000608@ramses-pyramidenbau.de>

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

On 21.11.2013 20:34, Ralf Ramsauer wrote:
> On 11/21/13 16:31, Vladimir 'phcoder' Serbinenko wrote:
>>
>> Why do you need offset and size options? keyfile option should be
>> repeteable. The whole array would be passed down and file would be
>> opened instead before reading password and concatebated with it unless
>> --no-password was specified as well. If you have remaining questions
>> feel free to ask here or on IRC.
>>
> See man 8 cryptsetup:
>  /      --keyfile-offset value//
> //              Skip value bytes at the beginning of the key file. 
> Works with all commands that accepts key files.//
> //
> //       --keyfile-size, -l value//
> //              Read a maximum of value bytes from the key file. 
> Default is to read the whole file up to the compiled-in maximum that can
> be queried with --help. Supplying more data than the compiled-in maximum
> aborts the operation.//
> //
> //              This option is useful to cut trailing newlines, for
> example. If --keyfile-offset is also given, the size count starts after
> the offset.  Works with all commands that accepts key files./
> 
Cutting trailing newlines throuch such options is IMHO inelegant and
would require more scripting than we currently have. Also those options
result in ambiguous syntax if you have multiple keyfiles (like geli). I
think it's better to skip those options, at least for now.



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 291 bytes --]

      reply	other threads:[~2013-11-22  3:02 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-19 23:43 Keyfile Support for GRUBs LUKS Ralf Ramsauer
2013-11-20  1:31 ` Glenn Washburn
2013-11-20  1:55   ` Elliott Mitchell
2013-11-20  5:43     ` Glenn Washburn
2013-11-20  5:48       ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-11-20  7:02         ` Glenn Washburn
2013-11-20  7:36           ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-11-21  5:57             ` Glenn Washburn
2013-11-25 10:38             ` Darren J Moffat
2013-11-20  6:42       ` Elliott Mitchell
2013-11-20  6:52         ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-11-20 21:08         ` Glenn Washburn
2013-11-21 15:31 ` Vladimir 'phcoder' Serbinenko
2013-11-21 19:34   ` Ralf Ramsauer
2013-11-22  3:01     ` Vladimir 'φ-coder/phcoder' Serbinenko [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=528EC901.8000704@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).