From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Avoiding fsck.ext4 destruction of crypto_luks data
Date: Sat, 29 Dec 2012 12:52:22 +0100 [thread overview]
Message-ID: <20121229115221.GA25591@tansi.org> (raw)
In-Reply-To: <50DEB248.9040106@gmail.com>
On Sat, Dec 29, 2012 at 10:05:12AM +0100, Milan Broz wrote:
> On 12/29/2012 08:06 AM, Arno Wagner wrote:
> > On Fri, Dec 28, 2012 at 08:22:25PM +0100, Milan Broz wrote:
>
> > Ext2 superblock signatures are all not wiped. Test I ran:
>
> Backup signatures should not be problem, (from the fsck problem
> POV, not from security/old data on disk POV of course).
>
> Tools screams a lot if you want to use these only and primary
> signature is missing.
Yes, they should. I don't see this as a real problem.
> Anyway, for wiping signature please suggest wipefs(8),
> this tool is designed to wipe all known signatures.
Added. I also give long wipe instructions, but have now
wipefs as fast one.
Arno
> (I am trying to avoid linking cryptsetup to libblkid, but
> if this happens some time in future, cryptsetup can call wipefs
> directly.)
>
> IOW
> wipefs -a <device>
>
> should destroy all known signatures to blkid
> (by minimalistic writes, this is not full device
> wipe, so it is very quick).
>
> 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
----
One of the painful things about our time is that those who feel certainty
are stupid, and those with any imagination and understanding are filled
with doubt and indecision. -- Bertrand Russell
next prev parent reply other threads:[~2012-12-29 11:52 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
2012-12-29 7:06 ` Arno Wagner
2012-12-29 9:05 ` Milan Broz
2012-12-29 11:52 ` Arno Wagner [this message]
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=20121229115221.GA25591@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