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=-0.6 required=3.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS 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 D918DC74A35 for ; Thu, 11 Jul 2019 12:04:49 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 2CF6421019 for ; Thu, 11 Jul 2019 12:04:49 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (2048-bit key) header.d=chronox.de header.i=@chronox.de header.b="p2mj6ert" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728320AbfGKMEs (ORCPT ); Thu, 11 Jul 2019 08:04:48 -0400 Received: from mo4-p00-ob.smtp.rzone.de ([81.169.146.218]:30341 "EHLO mo4-p00-ob.smtp.rzone.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728427AbfGKMEs (ORCPT ); Thu, 11 Jul 2019 08:04:48 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1562846686; s=strato-dkim-0002; d=chronox.de; h=References:In-Reply-To:Message-ID:Date:Subject:Cc:To:From: X-RZG-CLASS-ID:X-RZG-AUTH:From:Subject:Sender; bh=QDS5m6ANTja1UHGsEZTYM5Uqcp3Q5tifOJ+FzapbgHU=; b=p2mj6ert5DYU2/pDGFn3m5hsdjkaPRT031SKXff0W83OSFfYVT9WRo2K5EIQlLWsru GZ2TO0ZsDotSnyx1d9SpnaV1Z8ygjubfNSRKjcg0CpiF0A8ZhAB4RsVSo1Ds2ClyXgcv lQHypijIeMXfmDIk5CcmreePPFluwOG2FcmoeqTX4oQ32WGpWmslqS0kK6ONTADr4oWe tqpJpUQop4GRM4+4PJ09c6DIO+JssW2SXX7qHWa2BZH36W9wMiOgYWcb27tu6h1qni0O 7m7CIeqzb1EaLh+kY5sb6wPmmFH4GzREcx4HA2vyarjyWKXJtyxs1/2quGth/ssi5Xsj WeeA== X-RZG-AUTH: ":P2ERcEykfu11Y98lp/T7+hdri+uKZK8TKWEqNyiHySGSa9k9xm0dNS3IdRcRALiq2+M=" X-RZG-CLASS-ID: mo00 Received: from tauon.chronox.de by smtp.strato.de (RZmta 44.24 DYNA|AUTH) with ESMTPSA id 9078d1v6BBqTwpr (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (curve secp521r1 with 521 ECDH bits, eq. 15360 bits RSA)) (Client did not present a certificate); Thu, 11 Jul 2019 13:52:29 +0200 (CEST) From: Stephan Mueller To: "Bhat, Jayalakshmi Manjunath" Cc: "linux-crypto@vger.kernel.org" Subject: Re: CAVS test harness Date: Thu, 11 Jul 2019 13:52:29 +0200 Message-ID: <3201120.NINpRaGeap@tauon.chronox.de> In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Sender: linux-crypto-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-crypto@vger.kernel.org Am Dienstag, 9. Juli 2019, 08:43:51 CEST schrieb Bhat, Jayalakshmi Manjunath: Hi Jayalakshmi, > Hi All, > > We are working on a product that requires NIAP certification and use IPSec > environment for certification. IPSec functionality is achieved by third > party IPsec library and native XFRM. Third party IPsec library is used for > ISAKMP and XFRM for IPsec. > > CAVS test cases are required for NIAP certification. Thus we need to > implement CAVS test harness for Third party library and Linux crypto > algorithms. I found the documentation on kernel crypto API usage. > > Please can you indication what is the right method to implement the test > harness for Linux crypto algorithms. > 1. Should I implement CAVS test > harness for Linux kernel crypto algorithms as a user space application that > exercise the kernel crypto API? > 2. Should I implement CAVS test harness as > module in Linux kernel? As I have implemented the full CAVS test framework I can tell you that the AF_ALG interface will not allow you to perform all tests required by CAVS. Thus you need to implement your own kernel module with its own interface. > > > Any information on this will help me very much on implementation. > > Regards, > Jayalakshmi Ciao Stephan