From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.2 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 869ACC32750 for ; Tue, 30 Jul 2019 22:29:29 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 5A87A206E0 for ; Tue, 30 Jul 2019 22:29:29 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728565AbfG3W32 (ORCPT ); Tue, 30 Jul 2019 18:29:28 -0400 Received: from helcar.hmeau.com ([216.24.177.18]:37528 "EHLO fornost.hmeau.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727512AbfG3W32 (ORCPT ); Tue, 30 Jul 2019 18:29:28 -0400 Received: from gondolin.me.apana.org.au ([192.168.0.6] helo=gondolin.hengli.com.au) by fornost.hmeau.com with esmtps (Exim 4.89 #2 (Debian)) id 1hsacY-0000Dg-3w; Wed, 31 Jul 2019 08:29:26 +1000 Received: from herbert by gondolin.hengli.com.au with local (Exim 4.80) (envelope-from ) id 1hsacV-000497-CR; Wed, 31 Jul 2019 08:29:23 +1000 Date: Wed, 31 Jul 2019 08:29:23 +1000 From: Herbert Xu To: Pascal Van Leeuwen Cc: "linux-crypto@vger.kernel.org" , "davem@davemloft.net" Subject: Re: Crypto API skcipher key size question Message-ID: <20190730222923.GC7595@gondor.apana.org.au> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-crypto-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-crypto@vger.kernel.org On Tue, Jul 30, 2019 at 04:51:15PM +0000, Pascal Van Leeuwen wrote: > Hi, > > Quick question about skcipher algorithms supporting only > a single keysize, i.e. having min_keysize = max_keysize: > > Do I need to do a key size check here or does the crypto > API already ensure the key size is between min and max? > (and therefore guaranteed to be always correct here) You don't need to. Cheers, -- Email: Herbert Xu Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt