Received-SPF: pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
From:   Stephan Mueller <smueller@chronox.de>
To:     "Bhat, Jayalakshmi Manjunath" <jayalakshmi.bhat@hp.com>
Cc:     "linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>
Subject: Re: DRBG CAVS using libkcapi
Date:   Wed, 27 May 2020 20:48:57 +0200
Message-ID: <4958358.O0iSefo5KS@tauon.chronox.de>
In-Reply-To: <CS1PR8401MB0646C32205BFF9D0E8B5CCC2F6B10@CS1PR8401MB0646.NAMPRD84.PROD.OUTLOOK.COM>
References: <CS1PR8401MB0646C32205BFF9D0E8B5CCC2F6B10@CS1PR8401MB0646.NAMPRD84.PROD.OUTLOOK.COM>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Sender: linux-crypto-owner@vger.kernel.org
Precedence: bulk

Am Mittwoch, 27. Mai 2020, 04:21:31 CEST schrieb Bhat, Jayalakshmi Manjunath:

Hi Jayalakshmi,

> Hi All,
> 
> I was going through libkcapi APIs to see if it can be used for DRBG CAVS
> validation. But I am thinking it cannot be. I also found cavs_driver.pl,
> this seems to depend on some kernel mode driver. Is it like I need to
> testmgr.c kind of an interface and that should be accessed by user mode.
> 
> Please can any confirm if my understandings are correct?

The libkcapi cannot be used for CAVS testing the DRBG. Also a number of other 
ciphers like the asymmetric ciphers are not testable via libkcapi.

And yes, the Perl code refers to a kernel module that I developed but is 
private that allows full CAVS testing - this is the one that is used for all 
kernel crypto API CAVS/ACVP certificates that are out there.

Ciao
Stephan