From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] re-format existing luks partition
Date: Fri, 22 Nov 2013 16:33:37 +0100 [thread overview]
Message-ID: <20131122153337.GA13570@tansi.org> (raw)
In-Reply-To: <l6np5b$j4p$1@ger.gmane.org>
On Fri, Nov 22, 2013 at 15:19:33 CET, Robert Nichols wrote:
> On 11/22/2013 05:49 AM, shmick@riseup.net wrote:
[...]
> >>Also there are some fixes ready for reencryption tool on the way so you
> >>may be also interested waiting for 1.6.3 release in coming weeks.
> >
> >i shall wait around for some updates
> >just finally as an aside, is this method truly safe compared to starting
> >again ?
>
> Safer and simpler just to start over with a luksFormat, as you proposed.
It is simpler. As to safer, neither is safe without a good backup.
Arno
--
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
----
There are two ways of constructing a software design: One way is to make it
so simple that there are obviously no deficiencies, and the other way is to
make it so complicated that there are no obvious deficiencies. The first
method is far more difficult. --Tony Hoare
next prev parent reply other threads:[~2013-11-22 15:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-22 8:26 [dm-crypt] re-format existing luks partition shmick
2013-11-22 10:33 ` Ondrej Kozina
2013-11-22 11:49 ` shmick
2013-11-22 14:19 ` Robert Nichols
2013-11-22 15:33 ` Arno Wagner [this message]
2013-11-26 12:06 ` [dm-crypt] open ext-2/3/4 luks container, ext2fsd + FreeOTFE in Windows shmick
2013-11-26 12:34 ` Milan Broz
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=20131122153337.GA13570@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