From: "Mcnamara, John" <john.mcnamara@intel.com>
To: "Mcnamara, John" <john.mcnamara@intel.com>,
Brandon Lo <blo@iol.unh.edu>,
"Zhang, Roy Fan" <roy.fan.zhang@intel.com>
Cc: dev <dev@dpdk.org>, "Kovacevic, Marko" <marko.kovacevic@intel.com>
Subject: RE: [dpdk-dev] Question Regarding FIPS Validation in DPDK
Date: Thu, 2 Dec 2021 14:45:17 +0000 [thread overview]
Message-ID: <DM6PR11MB32272A72FB1250EF6C3BAABAFC699@DM6PR11MB3227.namprd11.prod.outlook.com> (raw)
In-Reply-To: <DM6PR11MB32279893059B20DBB03CB491FC699@DM6PR11MB3227.namprd11.prod.outlook.com>
> -----Original Message-----
> From: Mcnamara, John <john.mcnamara@intel.com>
> Sent: Thursday, December 2, 2021 8:45 AM
> To: Brandon Lo <blo@iol.unh.edu>; Zhang, Roy Fan <roy.fan.zhang@intel.com>
> Cc: dev <dev@dpdk.org>; Kovacevic, Marko <marko.kovacevic@intel.com>
> Subject: RE: [dpdk-dev] Question Regarding FIPS Validation in DPDK
>
> > -----Original Message-----
> > From: dev <dev-bounces@dpdk.org> On Behalf Of Brandon Lo
> > Sent: Wednesday, November 3, 2021 5:45 PM
> > To: Kovacevic, Marko <marko.kovacevic@intel.com>
> > Cc: dev <dev@dpdk.org>
> > Subject: [dpdk-dev] Question Regarding FIPS Validation in DPDK
> >
> > Hello,
> >
> > I have been able to use Cisco's libacvp tool to retrieve test vectors
> > from the NIST ACVP API.
> > However, after building the dpdk-fips_validation example and reading
> > through its documentation, it seems like the example application is
> > unable to parse the request files due to them being in a different
> format.
> > Currently, the ACVP API will supply request files in json format.
> >
> > The example app documentation says that the request file must be in
> > CAVS
> > 21.0 format. I have not been able to find a specification for this
> > format to compare.
> > Does the current version of the dpdk-fips_validation example support
> > the API's test vectors in json format?
>
>
> At the time the dpdk-fips_validation tool was written the test vectors
> weren't available in JSON format, and, to the best of my knowledge, there
> was a format specification (which is why there is different parsing for
> different algorithms). We (the community) should probably move to the JSON
> format. Adding Fan Zhang since I think this was discussion in the
> community previously.
Sorry I meant to say " to the best of my knowledge, there *wasn't* a format specification" available.
John
next prev parent reply other threads:[~2021-12-02 14:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-03 17:44 Brandon Lo
2021-12-02 8:44 ` Mcnamara, John
2021-12-02 14:45 ` Mcnamara, John [this message]
2021-12-03 18:44 ` Brandon Lo
2021-12-06 8:49 ` Mcnamara, John
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=DM6PR11MB32272A72FB1250EF6C3BAABAFC699@DM6PR11MB3227.namprd11.prod.outlook.com \
--to=john.mcnamara@intel.com \
--cc=blo@iol.unh.edu \
--cc=dev@dpdk.org \
--cc=marko.kovacevic@intel.com \
--cc=roy.fan.zhang@intel.com \
/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;
as well as URLs for NNTP newsgroup(s).