From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gmazyland@gmail.com>
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 hadx9ueTLr3m for <dm-crypt@saout.de>;
 Wed, 22 May 2013 17:28:32 +0200 (CEST)
Received: from mail-ea0-x22a.google.com (mail-ea0-x22a.google.com
 [IPv6:2a00:1450:4013:c01::22a])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (No client certificate requested)
 by mail.saout.de (Postfix) with ESMTPS
 for <dm-crypt@saout.de>; Wed, 22 May 2013 17:28:32 +0200 (CEST)
Received: by mail-ea0-f170.google.com with SMTP id f15so1209787eak.15
 for <dm-crypt@saout.de>; Wed, 22 May 2013 08:28:31 -0700 (PDT)
Received: from [192.168.2.18] (56.157.broadband5.iol.cz. [88.100.157.56])
 by mx.google.com with ESMTPSA id c41sm7106767eeu.8.2013.05.22.08.28.28
 for <dm-crypt@saout.de>
 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
 Wed, 22 May 2013 08:28:30 -0700 (PDT)
Message-ID: <519CE41B.5030205@gmail.com>
Date: Wed, 22 May 2013 17:28:27 +0200
From: Milan Broz <gmazyland@gmail.com>
MIME-Version: 1.0
References: <CACv9p5qPY9Q+=eW7-zVsuGsp3ryxRfxFujNS4PgRocpsqM=D5A@mail.gmail.com>
 <20130522143345.GB26551@tansi.org>
In-Reply-To: <20130522143345.GB26551@tansi.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [dm-crypt] luksAddKey successful but not working
List-Id: <dm-crypt.saout.de>
List-Unsubscribe: <http://www.saout.de/mailman/options/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=unsubscribe>
List-Archive: <http://www.saout.de/pipermail/dm-crypt/>
List-Post: <mailto:dm-crypt@saout.de>
List-Help: <mailto:dm-crypt-request@saout.de?subject=help>
List-Subscribe: <http://www.saout.de/mailman/listinfo/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=subscribe>
To: dm-crypt@saout.de

On 05/22/2013 04:33 PM, Arno Wagner wrote:
> A look into the man-page of cryptsetup shows that luksAddKey does
> not write the key-file, but reads it. I am surprised though that
> cryptsetup does not complain that the file is missing. With my
> system (cryptsetup 1.6.0) it does:
> 
> # cryptsetup luksAddKey /dev/loop0 keyfile
> Enter any passphrase:
> Failed to open key file.    <---
> #

RHEL5 has very old cryptsetup (based on 1.0.3 version) and it is impossible
to rebase there to a new version.
You can create a bug requesting to fix this issue in RH bugzilla though...

Milan