Received-SPF: pass (google.com: best guess record for domain of linux-crypto-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
From:   "Bhat, Jayalakshmi Manjunath" <jayalakshmi.bhat@hp.com>
To:     Stephan Mueller <smueller@chronox.de>
CC:     "linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>
Subject: RE: CAVS test harness
Thread-Topic: CAVS test harness
Thread-Index: AdU2IaQXtQPkG6HVRT2zauBDH3qftABvXlyAAABAX4AABvU+0A==
Date:   Thu, 11 Jul 2019 15:22:00 +0000
Message-ID: <TU4PR8401MB05445179722F462CD8C05AB0F6F30@TU4PR8401MB0544.NAMPRD84.PROD.OUTLOOK.COM>
References: <TU4PR8401MB0544875B118D39899547FDEFF6F10@TU4PR8401MB0544.NAMPRD84.PROD.OUTLOOK.COM>
 <3201120.NINpRaGeap@tauon.chronox.de> <1782078.ZURsmYODYl@tauon.chronox.de>
In-Reply-To: <1782078.ZURsmYODYl@tauon.chronox.de>
Accept-Language: en-US
Content-Language: en-US
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 74ef4cd2-c76f-4e49-3b83-08d706138558
X-MS-Exchange-CrossTenant-originalarrivaltime: 11 Jul 2019 15:22:00.6280
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: ca7981a2-785a-463d-b82a-3db87dfc3ce6
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: jayalakshmi.bhat@hp.com
X-MS-Exchange-Transport-CrossTenantHeadersStamped: TU4PR8401MB0703
X-MC-Unique: FkR16nKtOaWLM88BpKMpJA-1
X-Mimecast-Spam-Score: 0
Content-Type: text/plain; charset=WINDOWS-1252
Content-Transfer-Encoding: quoted-printable
Sender: linux-crypto-owner@vger.kernel.org
Precedence: bulk
List-ID: <linux-crypto.vger.kernel.org>
X-Mailing-List: linux-crypto@vger.kernel.org

Hi Stephan,

Thank you very much for the reply. Yes we would need to write the test for =
AEC (ECB,CBC,CTR) 128 and 256 bits, SHA-1, SHA-2 (256,384 and 512), HMAC, D=
RBG and also for key derivation functions.
We are planning to write netlink based kernel module to receive the data (t=
est vector input) from the user space and process the data and generate the=
 result, pass it on to user space.

I wanted to know if this sounds a reasonable approach?

Thanks in advance,
Jayalakshmi


-----Original Message-----
From: Stephan Mueller <smueller@chronox.de>=20
Sent: Thursday, July 11, 2019 5:30 PM
To: Bhat, Jayalakshmi Manjunath <jayalakshmi.bhat@hp.com>
Cc: linux-crypto@vger.kernel.org
Subject: Re: CAVS test harness

Am Donnerstag, 11. Juli 2019, 13:52:29 CEST schrieb Stephan Mueller:

Hi,

> Am Dienstag, 9. Juli 2019, 08:43:51 CEST schrieb Bhat, Jayalakshmi
> Manjunath:
>=20
> Hi Jayalakshmi,
>=20
> > Hi All,
> >=20
> > We are working on a product that requires NIAP certification and use=20
> > IPSec environment for certification. IPSec functionality is achieved=20
> > by third party IPsec library and native XFRM. Third  party IPsec=20
> > library is used for ISAKMP and XFRM for IPsec.
> >=20
> > CAVS test cases are required for NIAP certification.  Thus we need=20
> > to implement CAVS test harness for Third party library and Linux=20
> > crypto algorithms. I found the documentation on kernel crypto API usage=
.
> >=20
> > Please can you indication what is the right method to implement the=20
> > test harness for Linux crypto algorithms.
> > 1.=09Should I implement CAVS test
> > harness for Linux kernel crypto algorithms as a user space=20
> > application that exercise the kernel crypto API?
> > 2.=09Should I implement  CAVS test harness as
> > module in Linux kernel?
>=20
> As I have implemented the full CAVS test framework I can tell you that=20
> the AF_ALG interface will not allow you to perform all tests required by =
CAVS.
>=20
> Thus you need to implement your own kernel module with its own interface.

As a side note: if you only want to test the symmetric ciphers and the hash=
es/ HMACs, you can implement that with libkcapi easily.

However, if you are interested in testing the DRBG due to its relevance for=
 the GCM IV, you certainly need a kernel module.
>=20
> > Any information on this will help me very much on implementation.
> >=20
> > Regards,
> > Jayalakshmi
>=20
> Ciao
> Stephan


Ciao
Stephan