Return-Path: Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.17.9]) by mail.saout.de (Postfix) with ESMTP for ; Tue, 22 Sep 2009 18:08:16 +0200 (CEST) Date: Tue, 22 Sep 2009 18:14:49 +0200 From: Heinz Diehl Message-ID: <20090922161449.GA11479@fancy-poultry.org> References: <200909182039.44953.dmcrypt-list@tpesonen.net> <4AB3CE76.5040502@redhat.com> <200909182318.26032.dmcrypt-list@tpesonen.net> <200909221808.28418.dmcrypt-list@tpesonen.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200909221808.28418.dmcrypt-list@tpesonen.net> Subject: Re: [dm-crypt] Question on LUKS master key digest and its effect on?security List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: dm-crypt@saout.de On 22.09.2009, Tero Pesonen wrote: > Since there have been no comments on this, I was wondering if I should > rather send questions of this sort on scri.crypt or some such place > where these kind of topics are discussed? If so, is the iteration count > 10 for the PBKDF2 correct? (So that I am able to formulate my question > right and not pass on wrong information.) First, I'm by no means a professional programmer, and I'm not a LUKS/dmcrypt developer either. As far as I understand the source, MK iterations is the iterations used to derive the master key via PBKDF2 (mkDigestIterations), and what you can specify by using "--iter-time" is the iterations used to transform a passphrase into a key for one of the keyslots (passwordIterations), used to unlock the master key. Feel free to correct me if I'm wrong.