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 SBZfED9iLaaX for ; Wed, 18 Dec 2013 12:54:09 +0100 (CET) Received: from emh03.mail.saunalahti.fi (emh03.mail.saunalahti.fi [62.142.5.109]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.saout.de (Postfix) with ESMTPS for ; Wed, 18 Dec 2013 12:54:09 +0100 (CET) Received: from HA.koti (a88-112-68-74.elisa-laajakaista.fi [88.112.68.74]) by emh03.mail.saunalahti.fi (Postfix) with ESMTP id D88DB18884D for ; Wed, 18 Dec 2013 13:45:39 +0200 (EET) Received: from fld by HA.koti with local (Exim 4.80) (envelope-from ) id 1VtFZL-0001Gy-C8 for dm-crypt@saout.de; Wed, 18 Dec 2013 13:45:39 +0200 Date: Wed, 18 Dec 2013 13:45:39 +0200 From: FLD Message-ID: <20131218114539.GA4763@r00t3d.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Subject: [dm-crypt] Non-standard cipher mode List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: dm-crypt@saout.de I accidentally created a luks container using option --cipher aes-xts-plain64:sha512. Everything seems to be working correctly and luksDump shows: "Cipher mode: xts-plain64:sha512". I wonder if I should hexedit the header manually and replace the ":sha512" part with nulls since the proper format would be just "xts-plain64" since the cipher does not need a hash for the ESSIV?