From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <glkdd-dm-crypt@m.gmane.org>
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 gEmiXM7LEn0W for <dm-crypt@saout.de>;
 Tue, 18 Sep 2012 23:00:47 +0200 (CEST)
Received: from plane.gmane.org (plane.gmane.org [80.91.229.3])
 (using TLSv1 with cipher AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mail.saout.de (Postfix) with ESMTPS
 for <dm-crypt@saout.de>; Tue, 18 Sep 2012 23:00:46 +0200 (CEST)
Received: from list by plane.gmane.org with local (Exim 4.69)
 (envelope-from <glkdd-dm-crypt@m.gmane.org>) id 1TE4uW-0005Jm-0C
 for dm-crypt@saout.de; Tue, 18 Sep 2012 23:00:48 +0200
Received: from cpc1-rdng16-0-0-cust630.15-3.cable.virginmedia.com
 ([86.9.210.119]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian))
 id 1AlnuQ-0007hv-00
 for <dm-crypt@saout.de>; Tue, 18 Sep 2012 23:00:47 +0200
Received: from nick.battle by
 cpc1-rdng16-0-0-cust630.15-3.cable.virginmedia.com with local (Gmexim 0.1
 (Debian)) id 1AlnuQ-0007hv-00
 for <dm-crypt@saout.de>; Tue, 18 Sep 2012 23:00:47 +0200
From: Nick Battle <nick.battle@gmail.com>
Date: Tue, 18 Sep 2012 22:03:35 +0100
Message-ID: <k3andg$9s1$1@ger.gmane.org>
References: <k2vpn4$96e$1@ger.gmane.org> <50581FCC.3090504@suse.de>
 <505826F5.4010805@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
In-Reply-To: <505826F5.4010805@gmail.com>
Subject: Re: [dm-crypt] Migrating from loop AES to dm-crypt
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: dm-crypt@saout.de

OK, thanks everyone.

I just tried this again and it now works fine. I thought I tried several plain
"create" options, but... evidently not!

	cryptsetup create mapped <device> -c aes -s 128 -h sha256

Thanks again for the help!

-- 
Cheers,
-nick