From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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 sh8XwSaE5x_9 for ; Tue, 26 Nov 2013 13:06:39 +0100 (CET) Received: from mx1.riseup.net (mx1.riseup.net [198.252.153.129]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.saout.de (Postfix) with ESMTPS for ; Tue, 26 Nov 2013 13:06:38 +0100 (CET) Received: from fulvetta.riseup.net (fulvetta-pn.riseup.net [10.0.1.75]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.riseup.net", Issuer "Gandi Standard SSL CA" (not verified)) by mx1.riseup.net (Postfix) with ESMTPS id 3D6AF4567E for ; Tue, 26 Nov 2013 04:06:36 -0800 (PST) Message-ID: <52948EBF.6020604@riseup.net> Date: Tue, 26 Nov 2013 23:06:23 +1100 From: "shmick@riseup.net" MIME-Version: 1.0 References: <528F152D.5090205@riseup.net> In-Reply-To: <528F152D.5090205@riseup.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: [dm-crypt] open ext-2/3/4 luks container, ext2fsd + FreeOTFE in Windows List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: dm-crypt@saout.de does anybody have some working field notes they can pass on to get this working ? when i attempt to open the luks container, FreeOTFE can't do it in windows device manager the disk reports it must be initialised which will obviously destroy the luks header info i may have better luck with a FAT/NTFS fs but i'd prefer to keep it native to linux and just use read only in Windows my method was to simply first create the luks container, format it to ext4 and attempt to open in Windows with FreeOTFE could it be a permissions issue ? i thought not Re device manager results a long time ago i tried this with an ext4 partition and remember FreeOTFE mounted it ok, but Ext2fsd reported UUID=1000 pop up error and could not mount it