From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from awesome.dsw2k3.info (unknown [IPv6:2a01:198:661:1f::3]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.server123.net (Postfix) with ESMTPS for ; Thu, 11 Dec 2014 23:54:36 +0100 (CET) Date: Thu, 11 Dec 2014 23:54:28 +0100 From: Matthias Schniedermeyer Message-ID: <20141211225428.GA29801@citd.de> References: <20141211220453.GA24563@citd.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: [dm-crypt] question List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Sayler, Craig A. (AFRC-MI)[InuTeq, LLC]" Cc: "dm-crypt@saout.de" On 11.12.2014 22:07, Sayler, Craig A. (AFRC-MI)[InuTeq, LLC] wrote: > Ok Thank you of the response! No I have a system that someone removed the > key and there is no key left, is there a way to get in and get the data? If it is still open you can copy it (or backup it). If not and you don't have a header-backup i'm afraid that container is unrecoverable. > On 12/11/14 2:04 PM, "Matthias Schniedermeyer" wrote: > > >On 11.12.2014 18:30, Sayler, Craig A. (AFRC-MI)[InuTeq, LLC] wrote: > >> Is there a way to decrypt a drive permanently with out reinstalling? > > > >Yes. > > > >But the much safer way is: > >Backup, make a new filesystem on the previous backing-device & Restore > >from backup. > > > > > >The unsafe(!) 'inplace' method (that as an advantage doesn't need > >additional storage): > >Just open the container normally, 'dd' the mapped container over the > >backing device and pray that process isn't interruped. Because it will > >be a huge PITA if it gets interruped. > > > > > >But don't risk it, Backup & Restore is the way this should be done. > > > > > > > > > >-- > > > >Matthias > > _______________________________________________ > dm-crypt mailing list > dm-crypt@saout.de > http://www.saout.de/mailman/listinfo/dm-crypt -- Matthias