DPDK CI discussions
 help / color / mirror / Atom feed
From: Brandon Lo <blo@iol.unh.edu>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: ci@dpdk.org
Subject: Re: [PATCH 1/4] tools: add acvp_tool
Date: Tue, 25 Jan 2022 14:07:09 -0500
Message-ID: <CAOeXdvajBBYabx+Wh5w298S8qvzJt509w=c7uoBrpc3shhY_wA@mail.gmail.com> (raw)
In-Reply-To: <2089411.irdbgypaU6@thomas>

On Mon, Jan 24, 2022 at 3:24 PM Thomas Monjalon <thomas@monjalon.net> wrote:
>
> 24/01/2022 20:09, Brandon Lo:
> > This tool is used to interact with the ACVP API.
> >
> > Signed-off-by: Brandon Lo <blo@iol.unh.edu>
> > ---
> >  tools/acvp/__init__.py  |   0
> >  tools/acvp/acvp_tool.py | 315 ++++++++++++++++++++++++++++++++++++++++
>
> Did you write it from scratch?
> How does it compare with
> https://boringssl.googlesource.com/boringssl/+/refs/heads/master/util/fipstools/acvp/ACVP.md ?

Yes, I wrote it from scratch. It does a similar thing to the BoringSSL
FIPS tool, but this tool handles uploading the result from a file and
downloading the final verdict.
I haven't used the BoringSSL tool, but the bottom of the document says
it doesn't currently support uploading results from a file.
The tool I initially tried was libacvp, but I couldn't use it to
download only the vector sets that were supported by the FIPS
validation example in DPDK.


-- 
Brandon Lo
UNH InterOperability Laboratory
21 Madbury Rd, Suite 100, Durham, NH 03824
blo@iol.unh.edu
www.iol.unh.edu

  reply	other threads:[~2022-01-25 19:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-24 19:09 [PATCH 0/4] Add ACVP API tool Brandon Lo
2022-01-24 19:09 ` [PATCH 1/4] tools: add acvp_tool Brandon Lo
2022-01-24 20:24   ` Thomas Monjalon
2022-01-25 19:07     ` Brandon Lo [this message]
2022-01-25 20:33       ` Thomas Monjalon
2022-01-24 19:09 ` [PATCH 2/4] tools: add default config file for acvp_tool Brandon Lo
2022-01-24 19:09 ` [PATCH 3/4] tools: add requirements " Brandon Lo
2022-01-24 19:09 ` [PATCH 4/4] doc: add readme " Brandon Lo

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='CAOeXdvajBBYabx+Wh5w298S8qvzJt509w=c7uoBrpc3shhY_wA@mail.gmail.com' \
    --to=blo@iol.unh.edu \
    --cc=ci@dpdk.org \
    --cc=thomas@monjalon.net \
    /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

DPDK CI discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://inbox.dpdk.org/ci/0 ci/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ci ci/ http://inbox.dpdk.org/ci \
		ci@dpdk.org
	public-inbox-index ci

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.ci


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git