From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by mail.saout.de (Postfix) with ESMTP for ; Sat, 21 May 2011 21:33:04 +0200 (CEST) Message-ID: <4DD8136C.2090703@redhat.com> Date: Sat, 21 May 2011 21:33:00 +0200 From: Milan Broz MIME-Version: 1.0 References: <1306003236.10131.75.camel@localhost> In-Reply-To: <1306003236.10131.75.camel@localhost> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [dm-crypt] Using dmsetup directly instead of cryptsetup List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: dhvvcb@lavabit.com Cc: dm-crypt@saout.de On 05/21/2011 08:40 PM, dhvvcb@lavabit.com wrote: > Usually I run command > > cryptsetup -d /path/to/key -c aes-cbc-essiv:sha256 -s 256 create > hdd2 /dev/sdc > > and /dev/mapper/hdd2 is created. > > I tried to follow the example given on home page > http://www.saout.de/misc/dm-crypt/ That page is pretty obsolete today, http://code.google.com/p/cryptsetup/ is home page now. Why do you want to use dmsetup? Anyway, cryptsetup -d /key -c aes-cbc-essiv:sha256 -s 256 create x /dev/sdb is equivalent to echo 0 $(blockdev --getsz /dev/sdb) crypt aes-cbc-essiv:sha256 $(xxd -p -c 32