From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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 ; Fri, 24 Jun 2016 14:16:08 +0200 (CEST) References: <576C5689.4020200@dyne.org> <94146e8c-438a-85b5-0f29-ce02642af1ee@gmail.com> <576D03BB.9010301@dyne.org> <4897ac9d-a0a1-b04c-4b0c-81eab28a13b2@gmail.com> From: Police Terror Message-ID: <576D2485.9030502@dyne.org> Date: Fri, 24 Jun 2016 12:16:05 +0000 MIME-Version: 1.0 In-Reply-To: <4897ac9d-a0a1-b04c-4b0c-81eab28a13b2@gmail.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Subject: Re: [dm-crypt] cryptsetup with Python subprocess + pipes List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: dm-crypt@saout.de Here's the tool: https://github.com/RojavaCrypto/hiddencrypt Mostly proof of concept for now. Would be cool in the future to work something better out by hacking cryptsetup itself. Maybe if there's headerless volumes (that just look like random data). Multiple deniable Linux installs would be a killer feature. Milan Broz: > On 06/24/2016 11:56 AM, Police Terror wrote: >> Ahhh yes! Thank you Diagon and Milan. >> I've added now the -q switch. >> >> I looked at the pycryptsetup but 2 things: >> >> 1. It's not Python 3 >> 2. It's an extra dependency and not in the repos. > > Fedora has both Python3 and 2 builds but other > distros do not compile it probably. > > (It was designed for Anaconda installer mainly.) > > Milan > _______________________________________________ > dm-crypt mailing list > dm-crypt@saout.de > http://www.saout.de/mailman/listinfo/dm-crypt >