From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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 zyHKCfXJWl75 for ; Tue, 23 Apr 2013 18:18:24 +0200 (CEST) Received: from mail.jmho.de (mail.jmho.de [109.230.243.30]) by mail.saout.de (Postfix) with ESMTP for ; Tue, 23 Apr 2013 18:18:24 +0200 (CEST) Received: from slipstream.localnet (port-87-193-192-142.static.qsc.de [87.193.192.142]) by mail.jmho.de (Postfix) with ESMTPSA id 10BCA3A for ; Tue, 23 Apr 2013 18:18:24 +0200 (CEST) From: Jens-Michael Hoffmann Date: Tue, 23 Apr 2013 18:18:23 +0200 Message-ID: <4450852.6uU5N70hFn@slipstream> In-Reply-To: <2467145.0Six7fUZOk@slipstream> References: <3064141.nof2c3QVUk@slipstream> <20130423155213.GA17675@tansi.org> <2467145.0Six7fUZOk@slipstream> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="nextPart1700730.M5JmZcgQRo" Content-Transfer-Encoding: 7Bit Subject: Re: [dm-crypt] After reboot: "Command failed with code 22: Device /dev/md2 is not a valid LUKS device." List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: dm-crypt@saout.de This is a multi-part message in MIME format. --nextPart1700730.M5JmZcgQRo Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" > > Just out of curiosity: Is the cipher and key size combination (aes-xts- > plain64, 256 bit) the default or why did I have not to specify it to create > the mapping? (IIUC the metadata of plain mappings is not stored?) Never mind, I just realized that that was part of the destroyed luks device, so I guess the default cipher/key size of "cryptsetup create" is used now. Is there perhaps any way for converting the plain mapping into a luks mapping or would I just have to create a new luks device and copy data over? kind regards, Jens-Michael --nextPart1700730.M5JmZcgQRo Content-Transfer-Encoding: 7Bit Content-Type: text/html; charset="us-ascii"

>

> Just out of curiosity: Is the cipher and key size combination (aes-xts-

> plain64, 256 bit) the default or why did I have not to specify it to create

> the mapping? (IIUC the metadata of plain mappings is not stored?)

 

Never mind, I just realized that that was part of the destroyed luks device, so I guess the default cipher/key size of "cryptsetup create" is used now.

 

Is there perhaps any way for converting the plain mapping into a luks mapping or would I just have to create a new luks device and copy data over?

 

 

kind regards,

Jens-Michael

 

--nextPart1700730.M5JmZcgQRo--