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 2/4] tools: add default config file for acvp_tool
Date: Mon, 24 Jan 2022 14:09:21 -0500	[thread overview]
Message-ID: <20220124190923.745577-3-blo@iol.unh.edu> (raw)
In-Reply-To: <20220124190923.745577-1-blo@iol.unh.edu>

This provides the user with a generic configuration to
get started. It will use the demo server and a basic AES-GCM
test.

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

diff --git a/tools/acvp/acvp_config.json b/tools/acvp/acvp_config.json
new file mode 100644
index 0000000..9339885
--- /dev/null
+++ b/tools/acvp/acvp_config.json
@@ -0,0 +1,23 @@
+{
+    "url": "https://demo.acvts.nist.gov",
+    "algorithms": [
+        {
+            "algorithm": "ACVP-AES-GCM",
+            "revision": "1.0",
+            "direction": ["encrypt"],
+            "keyLen": [128, 192, 256],
+            "tagLen": [128],
+            "aadLen": [0],
+            "ivGenMode": "8.2.2",
+            "ivGen": "internal",
+            "ivLen": [96],
+            "payloadLen": [
+                {
+                    "max": 65536,
+                    "min": 0,
+                    "increment": 256
+                }
+            ]
+        }
+    ]
+}
\ No newline at end of file
-- 
2.25.1


  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 ` Brandon Lo [this message]
2022-01-24 19:09 ` [PATCH 3/4] tools: add requirements file for acvp_tool 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=20220124190923.745577-3-blo@iol.unh.edu \
    --to=blo@iol.unh.edu \
    --cc=ci@dpdk.org \
    /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).