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

Filesystem Object #8

Open
hannestschofenig opened this issue Jul 20, 2024 · 1 comment
Open

Filesystem Object #8

hannestschofenig opened this issue Jul 20, 2024 · 1 comment

Comments

@hannestschofenig
Copy link
Collaborator

Is the use of a file system object a use case we want to support? If so, we need to be more precise of how this works.

E.g. COSWID supports file system item but do we want to reuse the concept from there?

@thomas-fossati
Copy link
Collaborator

thomas-fossati commented Jul 24, 2024

I don't think measured components should replicate CoSWID functionality.

The file-entry and directory-entry structures defined in Section 2.9.2 of RFC9393 are way too complex - i.e., they have too much cruft attached, and are recursive in nature.

Conceptually, what we need to borrow from CoSWID is something like fs-name, but fully qualified, as a component name.

For example:

[
  / id / [
    / name / "/etc/service.conf"
  ],
  / measurement / [
    / alg / "sha-256",
    / val / h'3996003d486fb91ffb056f7d03f2b2992b215b31dbe7af4b37
              3431fc7d319da3'
  ]
]

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

No branches or pull requests

2 participants