From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wi0-x22a.google.com (mail-wi0-x22a.google.com [IPv6:2a00:1450:400c:c05::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mail.server123.net (Postfix) with ESMTPS for ; Sun, 14 Dec 2014 19:16:00 +0100 (CET) Received: by mail-wi0-f170.google.com with SMTP id bs8so8599475wib.5 for ; Sun, 14 Dec 2014 10:16:00 -0800 (PST) Message-ID: <548DD3DD.2090502@gmail.com> Date: Sun, 14 Dec 2014 19:15:57 +0100 From: Milan Broz MIME-Version: 1.0 References: <20141211220453.GA24563@citd.de> In-Reply-To: <20141211220453.GA24563@citd.de> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Subject: Re: [dm-crypt] question List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Matthias Schniedermeyer , "Sayler, Craig A. (AFRC-MI)[InuTeq, LLC]" Cc: "dm-crypt@saout.de" On 12/11/2014 11:04 PM, Matthias Schniedermeyer wrote: > > 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. Just FYI... I wonder why I did not add this option "permanently decrypt" to cryptsetup-reencrypt. Reencrypt tool uses similar approach to dd just it can be safely interrupted and restarted. Added enhancement issue for it https://code.google.com/p/cryptsetup/issues/detail?id=236 Milan