From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.saout.de ([127.0.0.1]) by localhost (mail.saout.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2kj23QgrhtjI for ; Fri, 28 Dec 2012 20:22:28 +0100 (CET) Received: from mail-ea0-f181.google.com (mail-ea0-f181.google.com [209.85.215.181]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mail.saout.de (Postfix) with ESMTPS for ; Fri, 28 Dec 2012 20:22:28 +0100 (CET) Received: by mail-ea0-f181.google.com with SMTP id k14so4523383eaa.40 for ; Fri, 28 Dec 2012 11:22:28 -0800 (PST) Message-ID: <50DDF171.1080807@gmail.com> Date: Fri, 28 Dec 2012 20:22:25 +0100 From: Milan Broz MIME-Version: 1.0 References: <20121227095229.GA9356@tansi.org> <20121228150430.GA17491@tansi.org> In-Reply-To: <20121228150430.GA17491@tansi.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [dm-crypt] Avoiding fsck.ext4 destruction of crypto_luks data List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Arno Wagner Cc: dm-crypt 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