From: Milan Broz <gmazyland@gmail.com>
To: Arno Wagner <arno@wagner.name>
Cc: dm-crypt <dm-crypt@saout.de>
Subject: Re: [dm-crypt] Avoiding fsck.ext4 destruction of crypto_luks data
Date: Fri, 28 Dec 2012 20:22:25 +0100 [thread overview]
Message-ID: <50DDF171.1080807@gmail.com> (raw)
In-Reply-To: <20121228150430.GA17491@tansi.org>
On 12/28/2012 04:04 PM, Arno Wagner wrote:
> I am thinking about a "basic LUKS setup" section for the FAQ
> that is more in the nature of a mini-howto. Things like blanking
> a previously used partition before a LUKS install seem to be
> not obvious to many people. Step-by-step instructions may help.
Wiping (whole) device (with some crypt random way) is still on TODO list.
But I believe that common signatures are wiped during LUKS format already
(we had several bugs related to this already) so it should never
happen that device contains ext4/swap/whatever signature parallel with
LUKS. (If so, please let me know, it is a bug.)
fsck can possibly use blkid and warn user
"Warning: device seems to contain xyz signature, do you really want...."
but this is feature for fsck (util-linux), not for cryptsetup.
(Anyway, I can ask util-linux maintainer later next year:)
Milan
next prev parent reply other threads:[~2012-12-28 19:22 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-27 6:12 [dm-crypt] Avoiding fsck.ext4 destruction of crypto_luks data Emily Williams
2012-12-27 9:35 ` ken
2012-12-27 9:52 ` Arno Wagner
2012-12-28 14:46 ` Sven Eschenberg
2012-12-28 15:04 ` Arno Wagner
2012-12-28 19:22 ` Milan Broz [this message]
2012-12-29 7:06 ` Arno Wagner
2012-12-29 9:05 ` Milan Broz
2012-12-29 11:52 ` Arno Wagner
2012-12-30 8:42 ` Sven Eschenberg
2012-12-30 9:39 ` Milan Broz
2012-12-30 10:53 ` Arno Wagner
2012-12-30 12:08 ` Sven Eschenberg
2012-12-30 12:25 ` Milan Broz
2012-12-30 13:19 ` Arno Wagner
2012-12-30 16:59 ` Emily Williams
2012-12-30 18:49 ` Matthias Schniedermeyer
2012-12-30 19:45 ` Arno Wagner
2012-12-31 6:37 ` Sven Eschenberg
2012-12-31 12:40 ` Richard
2012-12-27 20:29 ` Richard
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=50DDF171.1080807@gmail.com \
--to=gmazyland@gmail.com \
--cc=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