Linux cryptographic layer development
 help / color / mirror / Atom feed
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: CAVS test harness
Date: Fri, 12 Jul 2019 22:05:22 +0200	[thread overview]
Message-ID: <1973019.N0B863glP0@tauon.chronox.de> (raw)
In-Reply-To: <TU4PR8401MB0544B9D0BCD4C091857A1EAFF6F20@TU4PR8401MB0544.NAMPRD84.PROD.OUTLOOK.COM>

Am Freitag, 12. Juli 2019, 19:55:07 CEST schrieb Bhat, Jayalakshmi Manjunath:

Hi Jayalakshmi,

> Hi Stephan,
> 
> Thank you very much for the suggestions, I have another question, is it
> possible to implement MMT and MCT using kernel crypto API's.

Yes, for sure - I have successfully implemented all CAVS tests for all ciphers 
(see the CAVP validation list for the kernel crypto API).

> Also FCC and
> FCC functions.

I guess you mean FFC and ECC - yes, see the CAVP [2] web site.

Eric:

MCT - Monte Carlo Tests
MMT - Multi-Block Message Tests

In general, see [1] for all CAVS test specifications.

[1] https://csrc.nist.gov/projects/cryptographic-algorithm-validation-program

[2] https://csrc.nist.rip/groups/STM/cavp/validation.html

Ciao
Stephan



  parent reply	other threads:[~2019-07-12 20:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-09  6:43 CAVS test harness Bhat, Jayalakshmi Manjunath
2019-07-09 11:34 ` Gilad Ben-Yossef
2019-07-09 16:07   ` Bhat, Jayalakshmi Manjunath
2019-07-10 14:05     ` Gilad Ben-Yossef
2019-07-11 11:54   ` Stephan Mueller
2019-07-11 11:52 ` Stephan Mueller
2019-07-11 11:59   ` Stephan Mueller
2019-07-11 15:22     ` Bhat, Jayalakshmi Manjunath
2019-07-11 15:33       ` Stephan Mueller
2019-07-12 17:55         ` Bhat, Jayalakshmi Manjunath
2019-07-12 18:35           ` Eric Biggers
2019-07-13 15:49             ` Bhat, Jayalakshmi Manjunath
2019-07-12 20:05           ` Stephan Mueller [this message]
2019-07-13 16:04             ` Bhat, Jayalakshmi Manjunath

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1973019.N0B863glP0@tauon.chronox.de \
    --to=smueller@chronox.de \
    --cc=jayalakshmi.bhat@hp.com \
    --cc=linux-crypto@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox