Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pass CoRIM-specific context to extractors #298

Open
thomas-fossati opened this issue Jan 23, 2025 · 0 comments
Open

Pass CoRIM-specific context to extractors #298

thomas-fossati opened this issue Jan 23, 2025 · 0 comments
Labels
enhancement New feature or request

Comments

@thomas-fossati
Copy link
Contributor

Currently (d14e5af), the reference value and TAs extractors work on a triple level.

type IExtractor interface {
  RefValExtractor(comid.ValueTriples) ([]*handler.Endorsement, error)
  TaExtractor(comid.KeyTriple) (*handler.Endorsement, error)
  SetProfile(string)
}

The profile is the only variable that is made available from the global context.

Other information may become relevant at appraisal time and should be preserved, e.g.:

  • CoMID and CoRIM identifiers
  • notBefore/notAfter associated with the CoRIM manifest
  • CoRIM signer-related information

Another assumption backed into this interface is that ref-vale and trust anchors are only extracted from certain CoMID triples. This may not hold in two ways: other CoMID triples may be used, or other tags (e.g., CoTS) could be used. While the former is a bit speculative, the latter is probably what we want to have for CCA and PSA going forward.

This likely deserves a different tracking issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant