From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <mbroz@redhat.com>
Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28])
 by mail.saout.de (Postfix) with ESMTP
 for <dm-crypt@saout.de>; Thu, 16 Sep 2010 10:03:19 +0200 (CEST)
Message-ID: <4C91CF42.6000405@redhat.com>
Date: Thu, 16 Sep 2010 10:03:14 +0200
From: Milan Broz <mbroz@redhat.com>
MIME-Version: 1.0
References: <A5FF414BAA5D7440A998428F914DA601B44496ED4C@VMBX106.ihostexchange.net>
In-Reply-To: <A5FF414BAA5D7440A998428F914DA601B44496ED4C@VMBX106.ihostexchange.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [dm-crypt] Using --master-key-file option
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: Mikhail Malamud <mmalamud@freedomoss.com>
Cc: "'dm-crypt@saout.de'" <dm-crypt@saout.de>

On 09/16/2010 04:33 AM, Mikhail Malamud wrote:
> If I use this option, then cryptsetup no longer allows me to use generated key for slot 0 initialization insisting that I use passphrase instead. Is this expected behaviour?

For now yes, bug report is here.
http://code.google.com/p/cryptsetup/issues/detail?id=76

I'll fix it in next version.

Milan