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 RdZw1gtnGR5q for <dm-crypt@saout.de>;
 Tue, 19 Feb 2013 09:59:13 +0100 (CET)
Received: from mail-ee0-f43.google.com (mail-ee0-f43.google.com [74.125.83.43])
 (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>; Tue, 19 Feb 2013 09:59:13 +0100 (CET)
Received: by mail-ee0-f43.google.com with SMTP id c50so3487237eek.16
 for <dm-crypt@saout.de>; Tue, 19 Feb 2013 00:59:13 -0800 (PST)
Message-ID: <51233EC5.2070007@gmail.com>
Date: Tue, 19 Feb 2013 09:58:45 +0100
From: Milan Broz <gmazyland@gmail.com>
MIME-Version: 1.0
References: <CAFnMBaS7EB9rZ84afXsA=otitAqj3EehtLNnrm-ZnZenWw1GxQ@mail.gmail.com>
In-Reply-To: <CAFnMBaS7EB9rZ84afXsA=otitAqj3EehtLNnrm-ZnZenWw1GxQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [dm-crypt] the library and the binary do not agree on the
 cipher mode a truecrypt volume is created with
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: ".. ink .." <mhogomchungu@gmail.com>
Cc: dm-crypt@saout.de


On 19.2.2013 9:32, .. ink .. wrote:
> The source code for the "rrr" program is at: http://pastebin.com/CdG7KAuE

Thanks, I will check that.

Just please can you make there reports through issues page
http://code.google.com/p/cryptsetup/issues/list
and attach all test programs there?
(Not for this one but for future...)

This way it will be archived together and I can better trace it there.
(Also you will see link to resolution/fix commit immediatelly once it is fixed.)

Thanks,
Milan