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 8V39gBGQdY1o for ; Fri, 14 Sep 2012 06:19:08 +0200 (CEST) Received: from buhman.org (absdev-2-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:f35::2]) by mail.saout.de (Postfix) with ESMTP for ; Fri, 14 Sep 2012 06:19:07 +0200 (CEST) Date: Thu, 13 Sep 2012 23:19:06 -0500 From: Zack Buhman Message-ID: <20120914041906.GA3362@buhman.org> References: <20120914002117.GB2372@buhman.org> <20120914031851.GA29002@tansi.org> <20120914040553.GA2851@buhman.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20120914040553.GA2851@buhman.org> Subject: Re: [dm-crypt] Overwrote keyfile; Have master key; Recover data? List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: dm-crypt@saout.de On Fri, Sep 14, 2012 at 05:18:51AM +0200, Arno Wagner wrote: > but you will > need to make a new container after recovery, as your > master key is now publicly known and your data not secure > anymore. Nope; I flipped a few characters around ;P > Lets see, you have: > 0 7813523456 crypt aes-xts-plain bff82...76d4 0 9:127 4096 > ^^^^^^^^^^^^^ ^^^^^^^^^^^^ > cipher+mode key > A test with a loop file on my system gives: > 0 200704 crypt aes-cbc-essiv:sha256 9d....35 0 7:0 4096 > > Your old container does not use the defaults of the > cryptsetup sources, but the ones used by some distribution > or parameters set by yourself. Funny thing is, I was the one who specfied aes-xts-plain. > Make sure the new header is also aes-xts-plain, by > dumping the master key again. The key and cipher > parameter need to be the same, otherwise decryption will > not work. THAT'S IT! It works! Thank you very much Dr. Wagner; I can't tell you how grateful I am of you stating what should have been the obvious. Thanks again, Zack Buhman