Return-Path: Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.186]) by mail.saout.de (Postfix) with ESMTP for ; Fri, 14 Aug 2009 12:47:13 +0200 (CEST) Received: from liesel.fancy-poultry.org (localhost [127.0.0.1]) by liesel.fancy-poultry.org (Postfix) with ESMTP id BBE4218CD903C for ; Fri, 14 Aug 2009 12:50:39 +0200 (CEST) Date: Fri, 14 Aug 2009 12:50:39 +0200 Message-ID: <874osawtxc.wl%htd@fancy-poultry.org> From: Heinz Diehl In-Reply-To: References: MIME-Version: 1.0 (generated by EMIKO 1.14.1 - "Choanoflagellata") Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable Subject: Re: [dm-crypt] [Feature request] Support for "raw" key slots List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: dm-crypt@saout.de At Fri, 14 Aug 2009 09:36:09 +0200, Thomas B=E4chler wrote: > The iterated hashing process used in LUKS' key slots is useful for > (potentially weak) passphrases. However, it is useless if the key slot is= > locked with a cryptographically strong key file (like a file created from= > /dev/random). There's an option "--iter-time" where you can specify/reduce the iteration count. It's main purpose is well to slow down bruteforce attacks. Don't know if it's that what you're after.