DPDK CI discussions
 help / color / mirror / Atom feed
From: Brandon Lo <blo@iol.unh.edu>
To: ci@dpdk.org
Cc: Brandon Lo <blo@iol.unh.edu>
Subject: [PATCH 4/4] doc: add readme file for acvp_tool
Date: Mon, 24 Jan 2022 14:09:23 -0500
Message-ID: <20220124190923.745577-5-blo@iol.unh.edu> (raw)
In-Reply-To: <20220124190923.745577-1-blo@iol.unh.edu>

This readme file contains instructions to set up
and use the acvp_tool.

Signed-off-by: Brandon Lo <blo@iol.unh.edu>
 tools/acvp/README | 71 +++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 71 insertions(+)
 create mode 100644 tools/acvp/README

diff --git a/tools/acvp/README b/tools/acvp/README
new file mode 100644
index 0000000..0cd3acc
--- /dev/null
+++ b/tools/acvp/README
@@ -0,0 +1,71 @@
+The ACVP tool is a general tool for interacting with the NIST ACVP API
+in order to test different cryptographic implementations.
+It produces machine-readable output for parsing in a CI environment.
+There are also packages you need to download from the requirements.txt file:
+* pyotp
+* requests
+The tool expects that you have all the credential files from NIST:
+* Client certificate (usually a .cer file from NIST)
+* Key file for the certificate
+* Time-based one-time password seed file (usually a .txt file from NIST)
+The path to each file must be stored in an environment variable:
+$ACVP_SEED_FILE  =  Path to the TOTP seed .txt file    (given by NIST).
+$ACVP_CERT_FILE  =  Path to the client .cer/.crt file  (given by NIST).
+$ACVP_KEY_FILE   =  Path to the certificate key file   (generated by user).
+If you do not have the required files from NIST, you must email them
+to create demo credentials.
+After setting the environment variables as described in the
+"Requirements" section, you will need to edit the acvp_config.json file.
+The acvp_config.json file is expected to be a json object
+containing two keys: "url" and "algorithms"
+"url" must be the base URL string of the API you want to use.
+"algorithms" must be an array of algorithm objects as detailed in the
+ACVP API specification here:
+Now you can use the acvp_tool.py script to register a test session,
+upload the results, and download the verdict.
+To see all options available, use the --help flag.
+First, register and download a new test session with the tool:
+    acvp_tool.py --request $DOWNLOAD_PATH
+The file written to $DOWNLOAD_PATH will contain both the session information
+and the test vectors.
+You should use the DPDK FIPS validation example application to test
+the vectors in this file. The example application will generate
+the result file which is uploaded back to the ACVP API.
+After running tests with the vector file, you can submit the result:
+    acvp_tool.py --response $RESULT_PATH --upload
+where $RESULT_PATH is the path of the file containing the answers.
+Once you submit your results, you can do
+    acvp_tool.py --response $RESULT_PATH --verdict $VERDICT_PATH
+where $VERDICT_PATH is where you want to save the verdict information.
+The verdict file will contain the result of each test case submitted.
+You can also combine the options:
+    acvp_tool.py --response $RESULT_PATH --upload --verdict $VERDICT_PATH

      parent reply	other threads:[~2022-01-24 19:09 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
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 ` Brandon Lo [this message]

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:

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

  git send-email \
    --in-reply-to=20220124190923.745577-5-blo@iol.unh.edu \
    --to=blo@iol.unh.edu \
    --cc=ci@dpdk.org \


* 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 \
	public-inbox-index ci

Example config snippet for mirrors.
Newsgroup available over NNTP:

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