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 meGifT491fsr for ; Tue, 31 Jan 2012 16:34:05 +0100 (CET) Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by mail.saout.de (Postfix) with ESMTP for ; Tue, 31 Jan 2012 16:34:04 +0100 (CET) Message-ID: <4F2809E8.8060806@redhat.com> Date: Tue, 31 Jan 2012 16:34:00 +0100 From: Milan Broz MIME-Version: 1.0 References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [dm-crypt] cryptsetup not accepting plain passwd with -d option List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Nikhil AR Cc: dm-crypt@saout.de On 01/31/2012 03:49 PM, Nikhil AR wrote: > Hi, > > I have created an encrypted ISO image of a directory named data using the below command. > > # mkisofa -r data | aespipe -p3 -e aes256 3<./passphrase > data.iso ... > Is there a way to provide cryptsetup its password in a file when it is used in this manner? The problem is with password hashing. You need recent cryptsetup with loop-aes compatible support (in your case you do not need new kernel, it is not multi-key device) Just run cryptsetup loopaesOpen data.iso aesdev --key-file passphrase (no losetup needed, it should find loop automatically) Milan