From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gmazyland@gmail.com>
Received: from mail.saout.de ([127.0.0.1])
 by localhost (mail.saout.de [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id 9yonvdKluvS8 for <dm-crypt@saout.de>;
 Fri, 22 Nov 2013 10:17:49 +0100 (CET)
Received: from mail-ee0-x230.google.com (mail-ee0-x230.google.com
 [IPv6:2a00:1450:4013:c00::230])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (No client certificate requested)
 by mail.saout.de (Postfix) with ESMTPS
 for <dm-crypt@saout.de>; Fri, 22 Nov 2013 10:17:49 +0100 (CET)
Received: by mail-ee0-f48.google.com with SMTP id e49so446541eek.7
 for <dm-crypt@saout.de>; Fri, 22 Nov 2013 01:17:47 -0800 (PST)
Message-ID: <528F2138.6090205@gmail.com>
Date: Fri, 22 Nov 2013 10:17:44 +0100
From: Milan Broz <gmazyland@gmail.com>
MIME-Version: 1.0
References: <528CE6D7.8030005@riseup.net> <528D07E2.9040601@gmail.com>
 <528E1EDE.9010309@riseup.net> <528E57F1.6030709@gmail.com>
 <528F0A6C.9020209@riseup.net> <528F1246.1030201@gmail.com>
 <528F17F2.2010806@riseup.net>
In-Reply-To: <528F17F2.2010806@riseup.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [dm-crypt] 1.6.2 - waiting for zero, luksFormat hung
List-Id: <dm-crypt.saout.de>
List-Unsubscribe: <http://www.saout.de/mailman/options/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=unsubscribe>
List-Archive: <http://www.saout.de/pipermail/dm-crypt/>
List-Post: <mailto:dm-crypt@saout.de>
List-Help: <mailto:dm-crypt-request@saout.de?subject=help>
List-Subscribe: <http://www.saout.de/mailman/listinfo/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=subscribe>
To: "shmick@riseup.net" <shmick@riseup.net>
Cc: dm-crypt@saout.de, Peter Rajnoha <prajnoha@redhat.com>

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.

It works with upstream build, in fact, maximal interactive password length
can be seen in cryptsetup --help:
...
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