DM-Crypt Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "shmick@riseup.net" <shmick@riseup.net>
To: Milan Broz <gmazyland@gmail.com>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] 1.6.2 - waiting for zero, luksFormat hung
Date: Fri, 22 Nov 2013 22:56:13 +1100	[thread overview]
Message-ID: <528F465D.3090103@riseup.net> (raw)
In-Reply-To: <528F2138.6090205@gmail.com>



Milan Broz:
> On 11/22/2013 09:38 AM, shmick@riseup.net wrote:
> 
>>
>> why does luksFormat succeed using a simple short password and fail with
>> a more complex, longer one ?
>>
>> this occurs in parted magic boot cd from 28-02-2013
> 
> It seems that there is no free download. Sorry, cannot even try it. Ask them.

yes i believe the author of that went through some troubles a while back
- i was not aware you could not download any version anymore

> 
> It works with upstream build, in fact, maximal interactive password length
> can be seen in cryptsetup --help:

mind if i ask which distro you were able to successfully luksFormat to
in cryptsetup 1.6.2 issuing:

cryptsetup --debug --hash sha512 --cipher twofish-xts-plain64
--use-random --key-size 256 --iter-time 2000 luksFormat /dev/md0

what were your compile switches ?

> ...
> Default compiled-in key and passphrase parameters:
>         Maximum keyfile size: 8192kB, Maximum interactive passphrase length 512 (characters)
> Default PBKDF2 iteration time for LUKS: 1000 (ms)
> 
> Milan
> _______________________________________________
> dm-crypt mailing list
> dm-crypt@saout.de
> http://www.saout.de/mailman/listinfo/dm-crypt
> 

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

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-20 16:44 [dm-crypt] 1.6.2 - waiting for zero, luksFormat hung shmick
2013-11-20 19:05 ` Milan Broz
2013-11-21 14:55   ` shmick
2013-11-21 18:58     ` Milan Broz
2013-11-22  7:40       ` shmick
2013-11-22  8:13         ` Milan Broz
2013-11-22  8:38           ` shmick
2013-11-22  9:17             ` Milan Broz
2013-11-22 11:56               ` shmick [this message]
2013-11-22 13:11                 ` Milan Broz

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=528F465D.3090103@riseup.net \
    --to=shmick@riseup.net \
    --cc=dm-crypt@saout.de \
    --cc=gmazyland@gmail.com \
    /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