-
Notifications
You must be signed in to change notification settings - Fork 151
Description
Currently the interfaces pass a Verifier object. with the new implementation of https://github.com/mobilecoinfoundation/attestation for DCAP the same verifier object won't work for DCAP and EPID. We could make a wrapper verifier, but we don't know which underlying verifier we need until we get to the Report (also called Evidence) and the Report isn't seen until sometime later after the clients have provided the verifier object.
Based on initial design in, mobilecoinfoundation/mcips#65, it may be better to create a plain old data(POD) type for the MRENCLAVE|MRSIGNER values along with the advisories, and then pass this POD down to the point where verification happens. Building a verifier at the verify() location.
Thinking of modifying
| pub enum StatusVerifierConfig { |
Initial steps:
- Reshape
StatusVerifierConfig- Create common measurement types for attestation #3369
- Rename to
TrustedMeasurement, Create common measurement types for attestation #3369 - Move to a different module, the
TrustedMeasurementSetshould still persist for a JSON config, but theTrustedMeasurementtype should live elsewhere as it's not dedicated to the JSON usage anymore. Trusted Identity Types #3436 - Use dedicated ProductID and minimum SVN types from the mc-sgx-core-types crates. Currently they are both u16 and can be easily transposed. Trusted Identity Types #3436
- Add
TrustedMeasurementFromimpl toStatusVerifier#3377 - Change from passing verifier to passing measurements #3375