From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <PoliceTerror@dyne.org>
Received: from tupac2.dyne.org (tupac2.dyne.org [178.62.188.7])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (No client certificate requested)
 by mail.server123.net (Postfix) with ESMTPS
 for <dm-crypt@saout.de>; Fri, 24 Jun 2016 11:58:04 +0200 (CEST)
References: <576C5689.4020200@dyne.org> <576CC833.1080409@xoxy.net>
From: Police Terror <PoliceTerror@dyne.org>
Message-ID: <576D042A.60808@dyne.org>
Date: Fri, 24 Jun 2016 09:58:02 +0000
MIME-Version: 1.0
In-Reply-To: <576CC833.1080409@xoxy.net>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
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

dmsteg would be great but last updates are 2012 and my solution is way
simpler building off existing crypto primitives.

Diagon:
> 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
> 
> _______________________________________________
> dm-crypt mailing list
> dm-crypt@saout.de
> http://www.saout.de/mailman/listinfo/dm-crypt
>