DM-Crypt Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] question
Date: Sun, 14 Dec 2014 21:23:30 +0100	[thread overview]
Message-ID: <20141214202330.GA12006@tansi.org> (raw)
In-Reply-To: <548DD3DD.2090502@gmail.com>

On Sun, Dec 14, 2014 at 19:15:57 CET, Milan Broz wrote:
> 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.

This was likely just too obvious. Oversights like that happen to
me too. 
 
> Reencrypt tool uses similar approach to dd just it can be safely 
> interrupted and restarted.

Difference here would be that overwriting the header area
would need to be done last and data needs to be shifted 
forward by the data-offset. Having a header-sized unused 
area at the end should be non-critical.

> Added enhancement issue for it
> https://code.google.com/p/cryptsetup/issues/detail?id=236

Excellent.

Arno


> Milan
> _______________________________________________
> dm-crypt mailing list
> dm-crypt@saout.de
> http://www.saout.de/mailman/listinfo/dm-crypt

-- 
Arno Wagner,     Dr. sc. techn., Dipl. Inform.,    Email: arno@wagner.name
GnuPG: ID: CB5D9718  FP: 12D6 C03B 1B30 33BB 13CF  B774 E35C 5FA1 CB5D 9718
----
A good decision is based on knowledge and not on numbers. -- Plato

If it's in the news, don't worry about it.  The very definition of 
"news" is "something that hardly ever happens." -- Bruce Schneier

  reply	other threads:[~2014-12-14 20:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-11 18:30 [dm-crypt] question Sayler, Craig A. (AFRC-MI)[InuTeq, LLC]
2014-12-11 22:04 ` Matthias Schniedermeyer
2014-12-11 22:07   ` Sayler, Craig A. (AFRC-MI)[InuTeq, LLC]
2014-12-11 22:54     ` Matthias Schniedermeyer
2014-12-12 12:12     ` Arno Wagner
2014-12-12 12:11   ` Arno Wagner
2014-12-12 12:59     ` Matthias Schniedermeyer
2014-12-13  0:21       ` Arno Wagner
2014-12-14 18:15   ` Milan Broz
2014-12-14 20:23     ` Arno Wagner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-05-26 20:17 Guy Rachmuth
2011-05-27 12:14 ` Arno Wagner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20141214202330.GA12006@tansi.org \
    --to=arno@wagner.name \
    --cc=dm-crypt@saout.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox