From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mout.web.de (mout.web.de [212.227.15.3]) (using TLSv1.2 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.saout.de (Postfix) with ESMTPS for ; Thu, 17 Apr 2014 20:52:30 +0200 (CEST) Message-ID: <535022ED.2090101@web.de> Date: Thu, 17 Apr 2014 20:52:29 +0200 From: Jan Janssen MIME-Version: 1.0 References: <53501984.9050004@web.de> <53501D1F.4040904@gmail.com> In-Reply-To: <53501D1F.4040904@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [dm-crypt] Detached header List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Milan Broz , dm-crypt@saout.de On 04/17/2014 08:27 PM, Milan Broz wrote: > On 04/17/2014 08:12 PM, Jan Janssen wrote: >> Hi, >> >> I'm experimenting with LUKS detached header and I had the problem that >> cryptsetup binary does not like regular files when provided with >> --header (both luksFormat and open). When I make a manual losetup with >> the same header file and provide the loop device to --header everything >> works fine. >> >> According to the man page, --header is supposed to work for regular >> files too. This should either get fixed or the manual page be updated. > > Detached header should works with regular files. > > Can you provide more info what is not working? Please post failing command with > added --debug and provide exact versions of cryptsetup. > > Milan > Sorry for the noise, I had a typo in the header file name. Jan