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 5zBUrjGHptsq for ; Sat, 29 Dec 2012 23:42:30 +0100 (CET) Received: from mail-ee0-f52.google.com (mail-ee0-f52.google.com [74.125.83.52]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mail.saout.de (Postfix) with ESMTPS for ; Sat, 29 Dec 2012 23:42:29 +0100 (CET) Received: by mail-ee0-f52.google.com with SMTP id d17so5623202eek.39 for ; Sat, 29 Dec 2012 14:42:29 -0800 (PST) Message-ID: <50DF71D2.2030802@gmail.com> Date: Sat, 29 Dec 2012 23:42:26 +0100 From: Milan Broz MIME-Version: 1.0 References: <50DF635C.90003@gmail.com> <20121229222438.GA5411@citd.de> In-Reply-To: <20121229222438.GA5411@citd.de> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [dm-crypt] [ANNOUNCE] cryptsetup 1.6.0-rc1 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Matthias Schniedermeyer Cc: dm-crypt , Milan Broz On 12/29/2012 11:24 PM, Matthias Schniedermeyer wrote: > 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. I am not sure if it was this way in previous kernels (skcipher was added later, IIRC first was only hash API) Anyway, I'll fix description in final release here. Thanks, Milan