From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephan Mueller Subject: Re: cbc(aes-aesni) a givcipher? Date: Wed, 19 Aug 2015 12:31:13 +0200 Message-ID: <1889024.x7b0Yn2QbV@myon.chronox.de> References: <3211314.vIIIpsQc2S@myon.chronox.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: linux-crypto@vger.kernel.org To: herbert@gondor.apana.org.au Return-path: Received: from mail.eperm.de ([89.247.134.16]:48137 "EHLO mail.eperm.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752431AbbHSKbR (ORCPT ); Wed, 19 Aug 2015 06:31:17 -0400 In-Reply-To: <3211314.vIIIpsQc2S@myon.chronox.de> Sender: linux-crypto-owner@vger.kernel.org List-ID: Am Mittwoch, 19. August 2015, 12:11:03 schrieb Stephan Mueller: Hi, > Hi Herbert, > > with the latest cryptodev-2.6 tree I find the following: > > name : cbc(aes) > driver : cbc(aes-aesni) > module : kernel > priority : 300 > refcnt : 1 > selftest : passed > internal : no > type : givcipher > async : no > blocksize : 16 > min keysize : 16 > max keysize : 32 > ivsize : 16 > geniv : eseqiv > > name : cbc(aes) > driver : cbc(aes-aesni) > module : cbc > priority : 300 > refcnt : 1 > selftest : passed > internal : no > type : blkcipher > blocksize : 16 > min keysize : 16 > max keysize : 32 > ivsize : 16 > geniv : > > > Note the type of the ciphers. With this, an allocation of cbc(aes-aesni) > does not work (ENOENT). Just a followup: I think I see how I triggered it; I used cbc(aes-aesni) with crypto_alloc_aead due to an accident. But that makes me think: would that be an issue for the AF_ALG interface? I.e. I try to use the algif_aead interface but provide cbc(aes-aesni) as a cipher name? > > Any ideas? -- Ciao Stephan