From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <devrana@zoho.com>
Received: from sender153-mail.zoho.com (sender153-mail.zoho.com
 [74.201.84.153])
 (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mail.server123.net (Postfix) with ESMTPS
 for <dm-crypt@saout.de>; Fri, 24 Jun 2016 07:58:41 +0200 (CEST)
References: <576C5689.4020200@dyne.org>
From: Diagon <saout.boxy@xoxy.net>
Message-ID: <576CC833.1080409@xoxy.net>
Date: Thu, 23 Jun 2016 22:42:11 -0700
MIME-Version: 1.0
In-Reply-To: <576C5689.4020200@dyne.org>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Sender: devrana@zoho.com
Subject: Re: [dm-crypt] cryptsetup with Python subprocess + pipes (saout: to
 exclusive)
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: dm-crypt@saout.de

On 06/23/2016 02:37 PM, Police Terror - PoliceTerror@dyne.org wrote:
> Hello,
>
> I'm trying to make a plausible deniability encryption wrapper around
> cryptsetup.
>
> [...]

Not what you're asking, but for this purpose, have you had a look at
dmsteg?  http://dmsteg.sourceforge.net/

/D