[dm-crypt] maximum keyfile size

[dm-crypt] maximum keyfile size

[.. ink ..]

"cryptsetup --help" says the maximum keyfile size 8192kB.

Does the above limit apply to users of the library too?
why that number, why not a good,round number of 10MB?

Re: [dm-crypt] maximum keyfile size

[Heinz Diehl]

On 28.06.2012, .. ink .. wrote: 

> "cryptsetup --help" says the maximum keyfile size 8192kB.

As far as I understand the crytpsetup sourcecode, the keyfile gets
hashed, and is therefore comparable with a passphrase. 8192k for a
keyfile seems massive overkill, assumed you have 256/512 bit
encryption, where it will be sufficient to generate a keyfile which
contains 32/64 random chars. 

> Does the above limit apply to users of the library too?

AFAIK this is a limit which is set at compile time, see "configure
--help". I assume it's not hardcoded.

> why that number, why not a good,round number of 10MB?

I dunno.

Re: [dm-crypt] maximum keyfile size

[.. ink ..]

> AFAIK this is a limit which is set at compile time, see "configure
> --help". I assume it's not hardcoded.
>

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.

Re: [dm-crypt] maximum keyfile size

[Milan Broz]

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

Re: [dm-crypt] maximum keyfile size

[Heinz Diehl]

On 28.06.2012, Milan Broz wrote: 

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

So the length of a keyfile is equivalent to the length of a
passphrase, or is there any difference which should let me choose a
bigger keyfile than one containing 64 chars for "maximum security",
assumed I'm using 512 bit encryption?

Re: [dm-crypt] maximum keyfile size

[Matthias Schniedermeyer]

On 28.06.2012 12:28, Heinz Diehl wrote:
> On 28.06.2012, Milan Broz wrote: 
> 
> > Passphrase is interactively entered string
> > (from real terminal, not stdint), keyfile is everything else.
> 
> So the length of a keyfile is equivalent to the length of a
> passphrase, or is there any difference which should let me choose a
> bigger keyfile than one containing 64 chars for "maximum security",
> assumed I'm using 512 bit encryption?

If you shoot for maximum security that means you need at last 512 bit of 
ENTROPHY not characters (per se). As there are "values/bits missing" (at 
least the "\n") a 64 char key can't have the full 512 bit entrophy.

But when using e.g. base64 encoding you can pack the full 512 bits of 
entrophy into 85.33 chars. Personally i round that up to 528 bit, to get 
an even 88 chars. For base64 encoding the length should be divisible by 
3, otherwise you still get 88 chars (in this case) but the rest is 
filled with one or two "=" (Which you could also strip, it's no like you 
you need to be able to decode the string.)

head -c 66 /dev/random | openssl base64 -A
which gets you 88 chars.
or
head -c 64 /dev/random | openssl base64 -A | tr -d =
which gets you 86 chars.

Case one has 528 bits of entropy.
Case two has 512 bits of entrophy + 4 "empty" bits.


Bis denn

-- 
Real Programmers consider "what you see is what you get" to be just as 
bad a concept in Text Editors as it is in women. No, the Real Programmer
wants a "you asked for it, you got it" text editor -- complicated, 
cryptic, powerful, unforgiving, dangerous.

Re: [dm-crypt] maximum keyfile size

[.. ink ..]

resending the email with below content to list, didnt check were i
sent the email and i ended up sending it not to the list

On Thu, Jun 28, 2012 at 7:17 AM, .. ink .. <mhogomchungu@gmail.com> wrote:
>> Passphrase is interactively entered string
>> (from real terminal, not stdint), keyfile is everything else.
>>
>
> i know ssh prevents reading passphrase from stdin and demands a "real terminal"
>
> I have just spent hours googling looking for any security problems
> that arise from not caring if the passphrase came from tty,file or
> pipe and havent found anything.Any person know of a link i can read up
> to get more info?.
>
> i tried with version 1.5.0 rc1 and 1.3.1 to see how cryptsetup behaves
> when it asks for a key interactively while started on a background and
> this is what i saw. There seem to be a buffer overflow somewhere.
>
> [root@mtz sbin]# ./cryptsetup luksOpen /dev/sdc1 xxx &
> [3] 29690
> [root@mtz sbin]# Enter passphrase for /dev/sdc1: pp
> Usage:  pp -t type [-a] [-i input] [-o output]
> -t type              Specify the input type (must be one of private-key,
>                     public-key, certificate, certificate-request,
>                     pkcs7, crl or name)
> -a                   Input is in ascii encoded form (RFC1113)
> -i input             Define an input file to use (default is stdin)
> -o output            Define an output file to use (default is stdout)
>
> [3]+  Stopped                 ./cryptsetup luksOpen /dev/sdc1 xxx
> [root@mtz sbin]#