From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gmazyland@gmail.com>
Received: from mail-ee0-x234.google.com (unknown
 [IPv6:2a00:1450:4013:c00::234])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (No client certificate requested)
 by mail.server123.net (Postfix) with ESMTPS
 for <dm-crypt@saout.de>; Thu, 22 May 2014 11:30:58 +0200 (CEST)
Received: by mail-ee0-f52.google.com with SMTP id e53so2305043eek.25
 for <dm-crypt@saout.de>; Thu, 22 May 2014 02:30:58 -0700 (PDT)
Message-ID: <537DBE78.9070706@gmail.com>
Date: Thu, 22 May 2014 11:08:08 +0200
From: Milan Broz <gmazyland@gmail.com>
MIME-Version: 1.0
References: <20140502063112.GC8574@tansi.org>
 <CAHeB2AmsSrsU7=YSpKqwr+2d7YQPzW932N63zf=E-On=JZC33A@mail.gmail.com>
In-Reply-To: <CAHeB2AmsSrsU7=YSpKqwr+2d7YQPzW932N63zf=E-On=JZC33A@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [dm-crypt] cryptsetup FAQ monthly pointer
List-Id: <dm-crypt.saout.de>
List-Unsubscribe: <http://www.saout.de/mailman/options/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=unsubscribe>
List-Archive: <http://www.saout.de/pipermail/dm-crypt/>
List-Post: <mailto:dm-crypt@saout.de>
List-Help: <mailto:dm-crypt-request@saout.de?subject=help>
List-Subscribe: <http://www.saout.de/mailman/listinfo/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=subscribe>
To: Cpp <tzornik@gmail.com>, "dm-crypt@saout.de" <dm-crypt@saout.de>

On 05/22/2014 09:26 AM, Cpp wrote:
> Do you think it would be convenient to implement a new *cryptsetup*
> routine that does all these steps in 2.19 combined?

In fact this is my plan, integrate proper device wipe into cryptsetup,
planned long time ago...

Milan