From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gmazyland@gmail.com>
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 Tv54ejaNfDlc for <dm-crypt@saout.de>;
 Thu, 23 Jan 2014 23:31:33 +0100 (CET)
Received: from mail-ea0-f169.google.com (mail-ea0-f169.google.com
 [209.85.215.169])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (No client certificate requested)
 by mail.saout.de (Postfix) with ESMTPS
 for <dm-crypt@saout.de>; Thu, 23 Jan 2014 23:31:33 +0100 (CET)
Received: by mail-ea0-f169.google.com with SMTP id l9so573639eaj.28
 for <dm-crypt@saout.de>; Thu, 23 Jan 2014 14:30:57 -0800 (PST)
Message-ID: <52E1981E.5070807@gmail.com>
Date: Thu, 23 Jan 2014 23:30:54 +0100
From: Milan Broz <gmazyland@gmail.com>
MIME-Version: 1.0
References: <ED2C3830-3668-4225-B84A-AAAA0F0873F6@offensive-security.com>
 <CAFnMBaQHCp+EnstW6t7OgwdWzXEx9rtY04nzyh8tVmyD31yc1g@mail.gmail.com>
 <638F1A81-8F17-4E18-8993-7F848EA84F08@offensive-security.com>
 <20140114043042.GA15870@tansi.org> <52D6EF1B.4020206@gmail.com>
 <52DEF745.5040507@freesources.org> <52E18912.7070808@gmail.com>
 <CAFnMBaT0PEUKpE3S5pYY=64OZXe+G_8aHJhWtcsvaEmmUyBW3w@mail.gmail.com>
In-Reply-To: <CAFnMBaT0PEUKpE3S5pYY=64OZXe+G_8aHJhWtcsvaEmmUyBW3w@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [dm-crypt] nuke password to delete luks header
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: ".. ink .." <mhogomchungu@gmail.com>
Cc: dm-crypt <dm-crypt@saout.de>

On 01/23/2014 11:11 PM, .. ink .. wrote:
> 
> speaking of "cryptsetup-reencrypt",any plans to expose its functionality through the library API?

TBH I have never thought about it, it was designed as a standalone tool for LUKS only.

Maybe it would be nice to have integrated this through libcryptsetup but I am afraid it means
a lot of code rewrite.

Milan