From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-x22a.google.com (mail-wm0-x22a.google.com [IPv6:2a00:1450:400c:c09::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.server123.net (Postfix) with ESMTPS for ; Thu, 19 Nov 2015 15:30:35 +0100 (CET) Received: by wmdw130 with SMTP id w130so242695037wmd.0 for ; Thu, 19 Nov 2015 06:30:34 -0800 (PST) References: From: Milan Broz Message-ID: <564DDD09.2010506@gmail.com> Date: Thu, 19 Nov 2015 15:30:33 +0100 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Subject: Re: [dm-crypt] cryptsetup 1.2 to 1.6 upgrade List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jose Thomas , dm-crypt@saout.de On 11/19/2015 02:07 PM, Jose Thomas wrote: > > $ ls -l /dev/shm/key.dat > -rw-------. 1 root root 16 Nov 19 05:03 /dev/shm/key.dat Your keyfile is only 16 bytes long, you need 32 bytes for 256bit key. (There was an bug in cryptsetup 1.2.0 where this was not reported and rest of key was zeroed.) Try to add these zeroes to your keyfile and repeat. (Like dd if=/dev/zero of= seek=16 bs=1 count=16 conv=notrunc ) But note your key is half-zeroed (since the beginning!). Milan