From: Brandon Lo <blo@iol.unh.edu>
To: marko.kovacevic@intel.com
Cc: dev <dev@dpdk.org>
Subject: [dpdk-dev] Question Regarding FIPS Validation in DPDK
Date: Wed, 3 Nov 2021 13:44:31 -0400 [thread overview]
Message-ID: <CAOeXdvYvXqJFp1ugpsPGveL=vguOar+602mju8wuRgvgGtWNyA@mail.gmail.com> (raw)
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?
Thanks,
Brandon
--
Brandon Lo
UNH InterOperability Laboratory
21 Madbury Rd, Suite 100, Durham, NH 03824
blo@iol.unh.edu
www.iol.unh.edu
next reply other threads:[~2021-11-03 17:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-03 17:44 Brandon Lo [this message]
2021-12-02 8:44 ` Mcnamara, John
2021-12-02 14:45 ` Mcnamara, John
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='CAOeXdvYvXqJFp1ugpsPGveL=vguOar+602mju8wuRgvgGtWNyA@mail.gmail.com' \
--to=blo@iol.unh.edu \
--cc=dev@dpdk.org \
--cc=marko.kovacevic@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).