SecureAggregationRound
Enums · AiDotNet.FederatedLearning.Privacy
The rounds of the Bonawitz et al. (2017) secure aggregation protocol, in order.
For Beginners
Each value names the next message a participant is waiting to send or receive. A participant that receives a message for the wrong round refuses it.
How It Works
“Practical Secure Aggregation for Privacy-Preserving Machine Learning” (CCS 2017), figure 4. The honest-but-curious
protocol runs rounds 0, 1, 2 and 4; ConsistencyCheck (round 3) belongs to the variant secure against
an actively malicious server and is not executed by this library.
Fields
| Field | Summary |
|---|---|
SecureAggregationRound AdvertiseKeys |
Round 0: each client publishes two Diffie-Hellman public keys (c_u^PK, s_u^PK). |
SecureAggregationRound Completed |
The protocol instance has finished (or aborted) and holds no further secrets. |
SecureAggregationRound ConsistencyCheck |
Round 3: signature-based consistency check of the malicious-server variant (not executed). |
SecureAggregationRound MaskedInputCollection |
Round 2: each client sends its masked input y_u. |
SecureAggregationRound ShareKeys |
Round 1: each client Shamir-shares its self-mask seed b_u and masking key s_u^SK. |
SecureAggregationRound Unmasking |
Round 4: surviving clients send the shares the server needs to remove the masks. |
int value__ |