-
Notifications
You must be signed in to change notification settings - Fork 4
Add TCG RIM extensions #40
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
base: main
Are you sure you want to change the base?
Changes from all commits
e2ea915
c3bf29c
f86e667
ec3a107
c34b2ba
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,33 @@ | ||
| // Copyright 2020 Contributors to the Veraison project. | ||
| // SPDX-License-Identifier: Apache-2.0 | ||
|
|
||
| package swid | ||
thomas-fossati marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
|
||
| // See https://github.com/sacmwg/draft-ietf-sacm-coswid/blob/master/concise-swid-rim-extension.cddl | ||
|
|
||
| type AnyURI string | ||
|
|
||
| type TcgRimReferenceMeasurementEntry struct { | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Could you please refer to the spec where this extension CDDL is defined ?
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. done in c34b2ba |
||
| PayloadType *TcgRimPayloadType `cbor:"59,keyasint,omitempty" json:"payload-type,omitempty"` | ||
| PlatformConfigurationURIGlobal *AnyURI `cbor:"60,keyasint,omitempty" json:"platform-configuration-uri-global,omitempty"` | ||
| PlatformConfigurationURILocal *AnyURI `cbor:"61,keyasint,omitempty" json:"platform-configuration-uri-local,omitempty"` | ||
| BindingSpecName string `cbor:"62,keyasint" json:"binding-spec-name"` | ||
| BindingSpecVersion string `cbor:"63,keyasint" json:"binding-spec-version"` | ||
| PlatformManufacturerID *uint64 `cbor:"64,keyasint,omitempty" json:"platform-manufacturer-id,omitempty"` | ||
| PlatformManufacturerName string `cbor:"65,keyasint" json:"platform-manufacturer-name"` | ||
| PlatformModelName string `cbor:"66,keyasint" json:"platform-model-name"` | ||
| PlatformVersion *uint64 `cbor:"67,keyasint,omitempty" json:"platform-version,omitempty"` | ||
| FirmwareManufacturerID *uint64 `cbor:"68,keyasint,omitempty" json:"firmware-manufacturer-id,omitempty"` | ||
| FirmwareManufacturerName *string `cbor:"69,keyasint,omitempty" json:"firmware-manufacturer-name,omitempty"` | ||
| FirmwareModelName *string `cbor:"70,keyasint,omitempty" json:"firmware-model-name,omitempty"` | ||
| FirmwareVersion *uint64 `cbor:"71,keyasint,omitempty" json:"firmware-version,omitempty"` | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Any reason why ? boot-events => [ * boot-event-entry ],
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. May be I am referring to this: https://datatracker.ietf.org/doc/html/draft-birkholz-rats-coswid-rim-02 This is out of sync to the reference you mentioned above...
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. this is definitely a question for @henkbirkholz |
||
| RIMLinkHash []byte `cbor:"72,keyasint" json:"rim-link-hash"` | ||
| } | ||
|
|
||
| type TcgRimPayloadType uint64 | ||
|
|
||
| const ( | ||
| TcgRimPayloadTypeDirect = TcgRimPayloadType(iota) | ||
| TcgRimPayloadTypeIndirect | ||
| TcgRimPayloadTypeHybrid | ||
| ) | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could this file go under extensions/ folder ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why do we need to create another package?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All extensions (for future) can reside there. Is it not much neater rather than residing in the base package ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The separation is not that clear cut: one still needs to put the extension structures inside the base package structures, so it's not like you have two independent packages that you can decide whether to compose (or not), you always have to have both.