From: Milan Broz <gmazyland@gmail.com>
To: Matthias Schniedermeyer <ms@citd.de>,
"Sayler, Craig A. (AFRC-MI)[InuTeq,
LLC]" <craig.a.sayler@nasa.gov>
Cc: "dm-crypt@saout.de" <dm-crypt@saout.de>
Subject: Re: [dm-crypt] question
Date: Sun, 14 Dec 2014 19:15:57 +0100 [thread overview]
Message-ID: <548DD3DD.2090502@gmail.com> (raw)
In-Reply-To: <20141211220453.GA24563@citd.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
next prev parent reply other threads:[~2014-12-14 18:16 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 [this message]
2014-12-14 20:23 ` Arno Wagner
-- 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=548DD3DD.2090502@gmail.com \
--to=gmazyland@gmail.com \
--cc=craig.a.sayler@nasa.gov \
--cc=dm-crypt@saout.de \
--cc=ms@citd.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