You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Among requisition fulfillment, the duchy should verify the ProtocolConfig from EDP to ensure both of them are using the exactly same ProtocolConfig.
The Kingdom assigns ProtocolConfig for every Computation. But EDPs receive the ProtocolConfig from the requisition list and Duchies receive ProtocolConfig from the measurement. It is possible that Kingdom provides two different ProtocolConfigs. Duchies and EDPs need the verification to match their ProtocolConfigs.
Component(s) affected
EDPs, EDP simulator, Duchy.
Potential Solution
EDP/EDP simulator: Fulfill requisitions along with entire ProtocolConfig or a fingerprint. Due the the nature of non-deterministic protobuf serialization, we need a sophisticated approach to generate the fingerprint.
Duchy: Compare ProtocolConfig or fingerprint in requisition requests with ProtocolConfig of computations.
Version Environment Additional context
The text was updated successfully, but these errors were encountered:
…ecretSharing protocol (#191)
For shuffle based secret sharing protocol, requisitions are fulfilled by
EDPs with either chunks of data (a blob) or a seed. The seed can be
expanded into a deterministic blob with the same PRNG by workers.
The change is back-compatible.
Also added ProtocolConfig in FulfillRequisitionRequest for this
issue(world-federation-of-advertisers/cross-media-measurement#1329).
Describe the bug
Among requisition fulfillment, the duchy should verify the ProtocolConfig from EDP to ensure both of them are using the exactly same ProtocolConfig.
The Kingdom assigns ProtocolConfig for every Computation. But EDPs receive the ProtocolConfig from the requisition list and Duchies receive ProtocolConfig from the measurement. It is possible that Kingdom provides two different ProtocolConfigs. Duchies and EDPs need the verification to match their ProtocolConfigs.
Component(s) affected
EDPs, EDP simulator, Duchy.
Potential Solution
EDP/EDP simulator: Fulfill requisitions along with entire ProtocolConfig or a fingerprint. Due the the nature of non-deterministic protobuf serialization, we need a sophisticated approach to generate the fingerprint.
Duchy: Compare ProtocolConfig or fingerprint in requisition requests with ProtocolConfig of computations.
Version
Environment
Additional context
The text was updated successfully, but these errors were encountered: