Acvp auto testing

.github/workflows/artifact_validation.yaml

@@ -24,23 +24,35 @@ jobs:
         with:
           name: Compatibility_oqs_csv
           path: ./output/
-  bc_validation:
+
+  acvts_validation:
     runs-on: ubuntu-latest
-    container: bcdocker2000/bc_hackathon_pqc
+    # Is this an appropriate dotnet image?
+    container: mcr.microsoft.com/dotnet/sdk:6.0
     steps:
       - name: Checkout code
         uses: actions/checkout@v4
-      - name: Test artifacts with BC
-        run: ./src/test_certs_r3_with_bc.sh
+        with:
+          path: ./pqc-certificates
+      - name: Checkout acvts code
+        uses: actions/checkout@v4
+        with:
+          repository: josephlukefahr/ACVP-Server
+          ref: jwl/versions-in-some-packages
+          path: ./ACVP-Server
+      - run: apt update && apt install zip unzip
+      - run: mkdir ./output
+      - run: /bin/bash ./pqc-certificates/src/test_certs_r3_with_acvts.sh ./pqc-certificates
       - name: Save artifacts
         uses: actions/upload-artifact@v4
         with:
-          name: Compatibility_bc_csv
-          path: ./output/
+          name: Compatibility_acvts_csv
+          path: ./output
+
   build_results_html:
     runs-on: ubuntu-latest
     container: ubuntu:latest
-    needs: [oqs_validation, bc_validation]
+    needs: [oqs_validation, acvts_validation]
     steps:
       - name: Checkout code
         uses: actions/checkout@v4
@@ -59,10 +71,10 @@ jobs:
         with: 
           name: Compatibility_oqs_csv
           path: output/
-      - name: Get BC results from previous job
+      - name: Get acvts results from previous job
         uses: actions/download-artifact@v4
         with: 
-          name: Compatibility_bc_csv
+          name: Compatibility_acvts_csv
           path: output/
       - name: Build compat matrix (r3)
         run: ./src/rebuild_results_certs_r3.sh
@@ -74,6 +86,7 @@ jobs:
         uses:  actions/upload-pages-artifact@v3
         with:
           path: ./docs/gh-pages
+
   publish_to_gh_pages:
     needs: build_results_html
     if: github.ref == 'refs/heads/master'

.gitignore

@@ -3,3 +3,11 @@ providers/entrust/default/artifacts
 providers/corey-digicert/default/artifacts
 providers/bc/java-artifacts
 providers/botan/default/artifacts
+**/artifacts*/
+**/output/
+
+# C-sharp artifacts
+src/nist-acvts-generator/bin/
+src/nist-acvts-generator/obj/
+src/nist-acvts-verifier/bin/
+src/nist-acvts-verifier/obj/

providers/nist-acvts-test/readme.md → providers/nist-acvts-generator/readme.md

@@ -52,3 +52,27 @@ dotnet test NIST.CVP.ACVTS.Libraries.Crypto.SLHDSA.Tests.csproj > ~/Downloads/pq
 - Unit test logs included as dilithium.log and slh-dsa.log
 - NIST code seems to interchange "ML-DSA" and "Dilithium"; not sure which algorithm is actually implemented; could this be causing the issues with those certificates?
 - Big disadvantage to this approach -- I cannot assert any claims related to the NIST code (not even sure which algorithm is implemented!); a NIST engineer who is familiar with the code should generate and contribute the artifacts
+
+### 20241013
+
+- Lots of work!
+- Refactored X.509 generation (based on unit test) into a separate program
+- Found that writing a verification tool is feasible
+- Generation tool located at `pqc-certificates/src/nist-acvts-generator`
+- Verification tool located at `pqc-certificates/src/nist-acvts-verifier`
+- Tools require ACVP-Server code to exist "adjacent" to pqc-certificates repo, i.e...
+```
+  /
+  = opt/
+  ====== ACVP-Server/
+  ====== pqc-certificates/
+```
+- Tools include relevant ACVP-Server projects as source packages
+- Tools support PEM (for _r3 scripts) and DER (for _r4 scripts) files
+- New X.509 certificates generated and zippd manually into `nist-acvts-generator` provider
+- Tools accomodate OIDs for FIPS 204 & FIPS 205 algorithms
+- **Still cannot assert any claims to the NIST code**; still would be good to have  NIST engineer verify that we're using the NIST code properly
+- Drafted an updated GitHub Actions file; not familiar with GitHub Actions, though, so need help with that part also
+- Also, I still need to amend the ACVP-Server code; relevant source packages do not specify version bounds for dependencies,
+which results in inconsistent version, and for me, that means compilation errors!  I added minimum versions to some dependencies,
+which fixes my problem; again, would be good to discuss with NIST POCs about merging these changes (or something similar)

providers/nist-acvts-test/setup_acvts_env.sh

@@ -0,0 +1,13 @@
+#!/bin/sh
+
+# if no input was provided, then working dir is the current dir
+if [ -z "$1" ]; then
+    workingdir="./"
+else
+    workingdir=$1
+fi
+
+rm $workingdir/Directory.Build.props 2>&1 > /dev/null
+rm $workingdir/Directory.Packages.props 2>&1 > /dev/null
+ln -s $workingdir/_config/Directory.Build.props
+ln -s $workingdir/_config/Directory.Packages.props