From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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 JNK8HeGlHnor for ; Sat, 29 Dec 2012 23:24:49 +0100 (CET) Received: from awesome.dsw2k3.info (awesome.dsw2k3.info [IPv6:2a01:198:661:1f::3]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.saout.de (Postfix) with ESMTPS for ; Sat, 29 Dec 2012 23:24:49 +0100 (CET) Date: Sat, 29 Dec 2012 23:24:38 +0100 From: Matthias Schniedermeyer Message-ID: <20121229222438.GA5411@citd.de> References: <50DF635C.90003@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <50DF635C.90003@gmail.com> Subject: Re: [dm-crypt] [ANNOUNCE] cryptsetup 1.6.0-rc1 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Milan Broz Cc: dm-crypt On 29.12.2012 22:40, Milan Broz wrote: > > WARNING: benchmark requires kernel userspace crypto API to be available > (kernel af_alg and algif_skcipher modules, introduced in Linux kernel 2.6.38). This message doesn't help at all when you have a kernel that doesn't have it enabled and thus you can't find any module by that name. (And you CAN have a kernel with it build in, no module in that case too) The option for algif_skcipher is: CONFIG_CRYPTO_USER_API_SKCIPHER "Cryptographic API" -> "User-space interface for symmetric key cipher algorithms" The other option (that is responsible for af_alg) is hidden and automatically 'select'ed by activating the option above. -- Matthias