search

ietf-rats-wg / draft-ietf-rats-eat-measured-component

Other
0 stars 0 forks source link

Filesystem Object #8

Open hannestschofenig opened 4 months ago

hannestschofenig commented 4 months ago

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 commented 4 months ago

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'
  ]
]