From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by mail.saout.de (Postfix) with ESMTP for ; Tue, 29 Sep 2009 12:23:47 +0200 (CEST) Message-ID: <4AC1E02F.6030502@redhat.com> Date: Tue, 29 Sep 2009 12:23:43 +0200 From: Milan Broz MIME-Version: 1.0 References: <1253863271-17642-1-git-send-email-ludwig.nussel@suse.de> <4AC105CC.4080209@redhat.com> <49a25c1e0909290303t5f220e32na7ec13d1d4b784ce@mail.gmail.com> In-Reply-To: <49a25c1e0909290303t5f220e32na7ec13d1d4b784ce@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [dm-crypt] [PATCH] When reading no single byte for the key abort. List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: anton ivanov Cc: dm-crypt@saout.de anton ivanov wrote: > what are you talking about? I tried with empty file as passphrase, > surely not working :) I didn't say that empty keyfile can be used as real passphrase (in luksFormat), but the verification (luksOpen) will fail with "No key available with this passphrase" and with the patch it fails with different error - error during reading key. I can imagine that some scripts can depend on this behaviour and there is no real need to change it. When you enter empty string from terminal, it does the same. Milan