All of lore.kernel.org
 help / color / mirror / Atom feed
From: Milan Broz <gmazyland@gmail.com>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] maximum keyfile size
Date: Thu, 28 Jun 2012 09:54:50 +0200	[thread overview]
Message-ID: <4FEC0DCA.9090604@gmail.com> (raw)
In-Reply-To: <CAFnMBaQUYM-eArGw=pLU+pyE2hqwoYovBRUDCxyF6yWMAo565Q@mail.gmail.com>


On 06/28/2012 09:01 AM, .. ink .. wrote:
>> AFAIK this is a limit which is set at compile time, see "configure
>> --help". I assume it's not hardcoded.

yes, all these limit are configurable through configure switches.

> cryptsetup 1.4.3 and 1.5.o-rc1 seem to have a typo in ./configure
> --help in the key size options
> 
> both read:
> 
>   --with-keyfile-size-maxkb
>                           default maximum keyfile size (in kilobytes) [8192]
>   --with-passphrase-size-max
>                           default maximum keyfile size (in kilobytes) [512]
> 
> 
> the explanation for passphrase size is talking about keyfile, not
> passphrase. It also seem to suggest the max passphrase length is
> 512000 bytes( characters) while cryptsetup --help says its 512
> characters.

Yes, copy&paste error, will fix it.

Passphrase is interactively entered string
(from real terminal, not stdint), keyfile is everything else.

You can overwrite keyfile limit with explicitly setting --keyfile-size.
(You cannot overwrite interactive password length though.)

Both limits apply even for library.

Milan

  reply	other threads:[~2012-06-28  7:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-28  3:36 [dm-crypt] maximum keyfile size .. ink ..
2012-06-28  6:34 ` Heinz Diehl
2012-06-28  7:01   ` .. ink ..
2012-06-28  7:54     ` Milan Broz [this message]
2012-06-28 10:28       ` Heinz Diehl
2012-06-28 11:36         ` Matthias Schniedermeyer
     [not found]       ` <CAFnMBaSBBGvhvGHkH=T1gd3RwRkSy75SyhG+zkPow_gA4uAhFA@mail.gmail.com>
2012-06-28 11:22         ` .. ink ..

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=4FEC0DCA.9090604@gmail.com \
    --to=gmazyland@gmail.com \
    --cc=dm-crypt@saout.de \
    /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.