> -----Original Message----- > From: Mcnamara, John <john.mcnam...@intel.com> > Sent: Thursday, December 2, 2021 8:45 AM > To: Brandon Lo <b...@iol.unh.edu>; Zhang, Roy Fan <roy.fan.zh...@intel.com> > Cc: dev <dev@dpdk.org>; Kovacevic, Marko <marko.kovace...@intel.com> > Subject: RE: [dpdk-dev] Question Regarding FIPS Validation in DPDK > > > -----Original Message----- > > From: dev <dev-boun...@dpdk.org> On Behalf Of Brandon Lo > > Sent: Wednesday, November 3, 2021 5:45 PM > > To: Kovacevic, Marko <marko.kovace...@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
