From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ee0-x232.google.com (mail-ee0-x232.google.com [IPv6:2a00:1450:4013:c00::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mail.saout.de (Postfix) with ESMTPS for ; Thu, 17 Apr 2014 20:27:46 +0200 (CEST) Received: by mail-ee0-f50.google.com with SMTP id c13so938192eek.37 for ; Thu, 17 Apr 2014 11:27:46 -0700 (PDT) Message-ID: <53501D1F.4040904@gmail.com> Date: Thu, 17 Apr 2014 20:27:43 +0200 From: Milan Broz MIME-Version: 1.0 References: <53501984.9050004@web.de> In-Reply-To: <53501984.9050004@web.de> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [dm-crypt] Detached header List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jan Janssen , dm-crypt@saout.de 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