Skip to content
Discussion options

You must be logged in to vote

I can't run the CLI test for you, but I can answer the part you said you care about most: what a recipient needs beyond plain file signing. There is also one thing in the current exporter that matters before any outer signature does.

1. The manifest does not yet bind the report to the evidence underneath it

In evidence_pipeline.py, EvidenceSource declares sha256: str = "" (L66), but:

  • nothing in the pipeline ever assigns it (the field name appears nowhere else in the file), and
  • to_dict() (L68-74) does not emit it, so save_manifest() (L130-147) writes only source_type, path, collected_at and record_count for each source.

So a signature over annex-iv-report.md, from BoundaryAttest, Sigstor…

Replies: 2 comments 3 replies

Comment options

You must be logged in to vote
3 replies
@Johnbjoseph-cybersec
Comment options

@cullenmeyers
Comment options

@Johnbjoseph-cybersec
Comment options

Answer selected by cullenmeyers
Comment options

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants