Contents / Information Theory / Secret Sharing and Secure Computation
Chapter 18
Secret Sharing and Secure Computation
Splitting a secret so that any t shares reveal it and any t−1 reveal nothing, and computing on data nobody is allowed to see.
Introduction
Splitting a secret so that any t shares reveal it and any t−1 reveal nothing, and computing on data nobody is allowed to see.
This chapter is read in one direction. The first half builds a single object — a linear threshold sharing of a field element, with a proof that unqualified sets learn exactly nothing — and the second half spends it: the BGW protocol for secure multiparty computation is Shamir's scheme plus two operations on shares, and the famous threshold is nothing more than the arithmetic of polynomial degrees. Read the second half asking, at every step, which property of the sharing is being used here.
18.1Threshold Secret Sharing
A secret sharing scheme splits a secret into pieces so that authorised coalitions can put it back together and unauthorised ones learn nothing at all. Everything hinges on making "nothing at all" a theorem rather than a hope, so we set the definitions up information-theoretically from the start.
Definition 18.1 (Access structure). Let be the participants. An access structure is a family of subsets, called authorised (or qualified), which is monotone:
Subsets not in are unauthorised. The -threshold structure is .
Monotonicity is not a technical convenience; it is forced. If can reconstruct the secret then so can any superset of — the extra participants can simply stay silent. A non-monotone rule ("these three may reconstruct, but not if the fourth is in the room") cannot be enforced by handing out data, because data cannot be taken back.
Definition 18.2 (Perfect secret sharing scheme). A dealer holds a secret drawn from a distribution on a set and, using private randomness , computes shares , giving to . Write . The scheme realises perfectly if
- (Correctness) for every there is a reconstruction function with with probability ; equivalently ;
- (Perfect privacy) for every ,
The mutual-information form is the one to remember, but in constructions it is easier to verify the following equivalent statement, which says the shares an unauthorised coalition sees are statistically unrelated to what was shared.
Proposition 18.3 (Three faces of perfect privacy). For an unauthorised set the following are equivalent.
- .
- and are independent random variables.
- For all secrets and all share vectors , .
Proof. (1) (2) is the standard fact that mutual information vanishes exactly for independent variables: is a relative entropy between the joint law and the product of the marginals, and a relative entropy is zero if and only if its two arguments coincide.
(2) (3): independence makes , the same number for both . (3) (2): if the conditional law of is a fixed distribution for every secret, then , so .∎
Condition (3) is the working criterion: the adversary's view has a distribution that does not mention the secret. It is also, in miniature, the simulation paradigm of the second half of this chapter — a view you can sample without knowing the secret is a view that does not contain the secret.
Intuition. Think of a safe whose combination should open only when three of five managers agree. Each manager is handed a slip of paper. Any three slips together name the combination exactly; any two slips are, as far as their holders can tell, two uniformly random strings that would have looked exactly the same no matter what the combination was. That last clause — would have looked exactly the same — is perfect privacy. It is stronger than "hard to invert"; there is nothing to invert.
The simplest non-trivial scheme realises the structure, where every participant is needed.
Theorem 18.4 (XOR sharing realises perfectly). Let the secret be . Draw independently and uniformly from and set
Then , and any of the shares are uniformly distributed on independently of .
Proof. Correctness is immediate: XOR-ing all shares cancels every twice and leaves .
For privacy fix an unauthorised set, i.e. any with ; let be the missing index. If , then is uniform and does not involve , so criterion (3) of Three faces of perfect privacy holds trivially. If , then consists of the pads together with . Condition on the pads that appear: the remaining randomness is , uniform and independent, and the map is a bijection of for every fixed and . Hence is uniform on and independent of the other components, for every value of . The conditional law of is therefore the uniform law regardless of , which is criterion (3).∎
Example 18.5 (A sharing by hand). Share the -bit secret between two people, and check both properties.
Solution. The dealer draws uniformly and sets , .
Reconstruction: . ✓
Privacy: suppose you hold only . For each of the eight candidate secrets there is exactly one pad producing what you see, and each pad had probability . So for all — the same number eight times — and by criterion (3) your posterior on equals your prior. ✓ □□
Pitfall. A frequently offered " scheme" sets , , . Any two shares do reconstruct, so correctness holds — but is unauthorised and already knows everything, so privacy fails completely. Correctness is easy; a scheme is only as good as the proof of its privacy clause.
Threshold structures are not the only ones we can realise. The following construction settles the general question, at a price we will quantify in the section Share Size, Verifiability, and Extensions.
Theorem 18.6 (Every monotone access structure is realisable). Let be any monotone access structure on participants with minimal authorised sets . Then is realised perfectly by the replication scheme: independently produce, for each , an XOR sharing of and hand its pieces to the members of . Participant 's share is the list of all pieces it received.
Proof. Correctness. If then for some , so the members of jointly hold every piece of the -th XOR sharing and can XOR them to get .
Privacy. Let . For each we have , so misses at least one piece of the -th sharing; by XOR sharing realises perfectly the pieces of that sharing held by are uniform and independent of . The sharings use independent randomness, so the whole of is a uniform string of the appropriate length whose distribution does not depend on . Criterion (3) applies.∎
Applying this to gives shares consisting of two pieces each, and applying it to in general gives shares of size secrets — exponential in . That is intolerable, and it is the reason the next section exists: replacing combinatorics by algebra collapses the share down to a single field element.
18.2Shamir's Polynomial Scheme
Shamir's idea (1979) is to hide the secret as the value at of a random low-degree polynomial and to hand each participant one other point of it. Recovering a polynomial of degree at most takes points and no fewer, so the threshold property is inherited from a theorem of linear algebra rather than engineered by hand.
Work in a finite field with . A field is essential: interpolation divides by differences of evaluation points, so those differences must be invertible, which fails in a ring like . The condition guarantees distinct nonzero evaluation points — nonzero because is reserved for the secret itself.
Theorem 18.7 (Lagrange interpolation). Let be distinct elements of a field and let be arbitrary. Then there is exactly one polynomial of degree at most with for all , namely
Proof. Existence. Each has degree , and : the numerator vanishes at every with , and at numerator and denominator agree. Hence . The denominators are nonzero because the are distinct, which is where the field structure is used.
Uniqueness. If and both work, has degree at most and distinct roots. A nonzero polynomial of degree over a field has at most roots (factor out repeatedly), so .∎
Evaluating at gives the form we will use over and over: the secret is a fixed linear combination of any shares,
with coefficients that depend only on which evaluation points were used — not on the secret, not on the randomness, not on the values. These recombination coefficients are public. Remember them; the whole of BGW is built on the fact that reconstruction is linear.
Method 18.8 (Shamir's dealing procedure).
- Fix with and public distinct nonzero points (usually ).
- Draw independently and uniformly from and set
- Give participant the share .
Theorem 18.9 (Shamir's scheme realises perfectly). For every the scheme above is a perfect -threshold scheme over : any shares reconstruct , and for any set with the vector is uniformly distributed on independently of .
Proof. Correctness. A set of participants holds pairs with distinct , and , so by Lagrange interpolation those pairs determine uniquely; then .
Privacy. Fix and fix a target vector . Fix any candidate secret . We count the polynomials the dealer could have drawn that are consistent with both.
The dealer's polynomial ranges over
Now the constraints together with the constraint are interpolation conditions at distinct points — distinct because each and the are distinct. By the uniqueness half of Lagrange interpolation there is exactly one polynomial of degree at most satisfying all of them. Hence
The right-hand side does not mention . So the conditional law of is uniform on for every secret, and criterion (3) of Three faces of perfect privacy gives .∎
Read the proof again with an eye on where the hypotheses were spent. Uniqueness of interpolation gave privacy; existence gave correctness. The same theorem does both jobs, from opposite ends. And the count shows more than independence: the adversary's view is uniform, so a simulator can produce it by drawing random field elements — the cleanest possible form of the simulation paradigm.
Example 18.11 (A sharing over ). Share with , , using over , and reconstruct from participants .
Solution. Shares, all arithmetic mod :
, , , , .
So the shares are .
Recombination from : the coefficients are
Then . ✓
Sanity check with a disjoint triple . Here , and because , so . Next , and . These sum to , as recombination coefficients must, since applied to the constant polynomial they must return .
Reconstructing: ✓ — the same secret from a completely different triple, as Shamir's scheme realises perfectly guarantees they must. □□
Pitfall. The evaluation points are public labels; the shares are the values . Publishing which participant holds which index costs nothing, but publishing a value destroys one degree of protection. Likewise, never reuse the same polynomial to share a second secret, and never give two participants the same — two equal indices are one share, not two.
The last property of the scheme is the one the MPC half consumes, and it is worth isolating.
Lemma 18.12 (Shamir sharing is linear). Suppose and are degree- polynomials sharing and at the same evaluation points, and let . Then is a degree- sharing of and is a degree- sharing of , and each participant computes its new share locally, as and .
Proof. Sums and scalar multiples of polynomials of degree at most have degree at most , and evaluation is linear: and . The constant terms behave the same way: , .∎
18.3Share Size, Verifiability, and Extensions
Perfection has a price, and it is paid in share length. The bound below is information-theoretic — no cleverness escapes it — and it explains why every deployed information-theoretic scheme stores as many bits per participant as the secret itself.
Proof. Perfect privacy at gives ; correctness at gives . Subtract:
Conditional mutual information never exceeds the conditional entropy of either argument, so . Finally conditioning cannot increase entropy, so .
For , every participant lies outside some set of size whose union with has size and is therefore qualified, so the bound applies to every share.∎
Corollary 18.14 (Shamir is size-optimal). For a uniform secret in , Shamir's scheme meets the bound with equality: bits.
Proof. By the privacy half of Shamir's scheme realises perfectly with , each single share is uniform on (take inside any unqualified set), so , which is .∎
Intuition. Why can a share not be shorter than the secret? Stand in the shoes of a coalition one member short. They know nothing — every secret is still equally likely. The moment the last member arrives, they know everything. So that one arriving share had to carry the entire remaining uncertainty by itself, and a message cannot carry more information than its own length.
Remark. The bound is about perfect schemes. Two escapes exist. Ramp schemes weaken privacy: an ramp scheme reconstructs from shares, leaks nothing below , and leaks partially in between, which lets shares be a factor smaller than the secret. Computational schemes encrypt the secret under a random key, share the key with Shamir, and distribute pieces of the ciphertext (Krawczyk); shares shrink to roughly , at the cost of resting on an assumption. Neither contradicts the theorem; each gives up one of its hypotheses.
A second cost is structural: the replication scheme of Every monotone access structure is realisable gives shares exponential in for threshold structures, while Shamir gives one field element. The general framework explaining why is linear algebra.
Definition 18.15 (Linear secret sharing scheme (LSSS)). A scheme is linear over if there is a matrix and an assignment of the rows to participants such that, with for uniform , the share of is the set of coordinates of belonging to 's rows. A set is qualified exactly when the target vector lies in the row span of restricted to 's rows.
Shamir is linear with the Vandermonde matrix of rows , and the recombination coefficients are exactly the coefficients expressing in that span. Linear schemes are equivalent to monotone span programs; whether every monotone structure has a polynomial-size linear scheme is open, and the best known general upper bound is sub-exponential rather than polynomial.
So far the dealer has been honest. Remove that assumption and correctness collapses: a corrupt dealer can hand out points that lie on no single low-degree polynomial, so that different qualified sets reconstruct different "secrets". Verifiable secret sharing fixes this.
Definition 18.16 (Verifiable secret sharing (VSS)). A VSS scheme adds to the dealing phase a public verification procedure such that
- (Binding/commitment) after dealing, there is a well-defined value such that every qualified set of honest participants reconstructs — even if the dealer is corrupt;
- (Validity) if the dealer is honest, ;
- (Privacy) if the dealer is honest, unqualified sets still learn nothing about .
Method 18.17 (Feldman VSS). Work in a group of prime order in which discrete logarithms are hard.
- The dealer chooses over and sends privately to .
- The dealer broadcasts the commitments , , …, .
- accepts its share if and only if
- If a participant's check fails it complains publicly; the dealer must reveal that share, and a dealer who cannot is disqualified.
Proposition 18.18 (The Feldman check is exactly consistency with a degree- polynomial). Given broadcast , a value passes the check at if and only if for the unique polynomial whose coefficients are the discrete logarithms of the .
Proof. Write (possible since generates ) and . Then
Since has prime order , the map is injective on , so holds if and only if .∎
Binding here is unconditional: the commitments determine as an element of of degree whatever the dealer does, so all accepted shares lie on one polynomial and every qualified set reconstructs its constant term. Privacy, however, is only computational — leaks to anyone who can take discrete logarithms, and even without that it identifies uniquely. Pedersen's commitment trades the two around.
Definition 18.19 (Pedersen commitment). With two generators of whose relative discrete logarithm is unknown to the committer, the commitment to with randomness is
Theorem 18.20 (Pedersen is perfectly hiding and computationally binding). For fixed , with uniform is uniformly distributed on , so a commitment reveals nothing whatsoever about . Moreover, anyone who opens one commitment in two ways can compute .
Proof. Hiding. generates (any non-identity element of a group of prime order does), so is a bijection ; multiplying by the fixed element is again a bijection. Hence the commitment is uniform on for every , which is criterion (3) of Three faces of perfect privacy once more.
Binding. Suppose with . Then . Here , since otherwise would force in a group of prime order. Therefore , computable from the two openings.∎
Pedersen VSS runs Feldman with in place of , the dealer additionally sharing the randomness polynomial; the verification identity is the same computation carried out in two exponents at once. The resulting scheme is perfectly private and binding only under the discrete-logarithm assumption — the mirror image of Feldman. Which you want depends on whether the secret must stay hidden forever (Pedersen) or the sharing must stay correct against an unbounded dealer (Feldman).
Example 18.21 (Running the Feldman check with small numbers). Let be the subgroup of order inside , generated by , so that exponents are read modulo . The dealer uses and over . Verify participant 's share.
Solution. Commitments. and , both broadcast; all group arithmetic is mod .
Share. , sent privately to participant .
Check. The left side is . The right side is
A corrupt dealer. Suppose the dealer had sent instead. Then , and participant complains. Sanity check: the check passed exactly at the value predicted by The Feldman check is exactly consistency with a degree- polynomial, and has order because , so exponent arithmetic mod is legitimate. □□
Example 18.22 (Refreshing shares without changing the secret). Shares leak over time: an adversary who breaks into one machine per month eventually collects of them. Show how the participants can replace all shares by fresh ones, without ever reconstructing and without a dealer.
Solution. Each participant picks a random polynomial of degree with zero constant term, , and sends privately to each .
Every participant updates its share to
Why it helps: old and new shares are related by a sharing of that is uniform among degree- polynomials vanishing at (as long as at least one came from an honest participant), so old shares combined with new shares still leave uniform. The adversary must now collect shares within a single epoch. Sanity check: setting all returns the original sharing, and evaluating at never involves the at all. □□
18.4The Secure Multiparty Computation Problem
Secret sharing hides data at rest. Secure multiparty computation (MPC) hides it while it is being used: parties, each holding a private input, want the value of a joint function and nothing else.
Definition 18.23 (Secure multiparty computation). Parties hold private inputs and wish to compute
by exchanging messages, so that
- (Correctness) every honest party outputs the correct , and
- (Privacy) the parties learn nothing about the inputs beyond what and their own inputs already imply.
The second clause is useless until "learn nothing beyond" is made mathematical, and the naive attempts fail. "The adversary cannot compute any " is too weak — leaking half of 's bits satisfies it. "The transcript is independent of the inputs" is too strong — the transcript determines , which depends on the inputs. The resolution, due to Goldwasser, Micali and Rackoff and refined by Goldreich, Micali and Wigderson, is comparative: measure the real protocol against an idealisation that is private by construction.
Definition 18.24 (The ideal functionality). In the ideal world an incorruptible trusted party receives over private channels, computes , returns to everyone, and forgets. An adversary corrupting a set of parties in the ideal world sees exactly and — by construction, nothing else exists to see.
Definition 18.25 (View and simulation-based security (semi-honest)). The view of party in a real execution is
its input, its random tape and every message it received. A protocol computes with perfect security against semi-honest adversaries corrupting at most parties if it is correct and, for every with , there is a probabilistic polynomial-time simulator such that for all inputs
the two distributions being identical. Replacing by "statistically close" gives statistical security, and by "computationally indistinguishable" gives computational security.
The definition is exactly the right one because it is an if-then about information: anything the coalition could deduce from its real view, it could equally deduce from a transcript it manufactured itself out of its own inputs and the output. Since the manufactured transcript plainly contains no extra information about the honest inputs, neither does the real one. Notice the family resemblance to the privacy proof of Shamir's scheme, where the adversary's view was uniform and so could be sampled without the secret: that proof was a simulator.
Intuition. Imagine the ideal world as a sealed room with a perfectly trustworthy clerk. You slide your number under the door, the clerk announces the answer, and the papers are burnt. A real protocol has no clerk; it is a conversation. The definition asks for a forger: someone who, knowing only what the clerk would have told you, can write a fake transcript of that conversation which you could not distinguish from the real one. If such a forger exists, the conversation told you nothing the clerk did not.
Pitfall. Privacy is "beyond what reveals", and can reveal a great deal. If is the average of three salaries and two parties collude, they subtract their own inputs and recover the third exactly. That is not a protocol failure — the ideal functionality leaks it too. Choosing so that its output is safe to publish is a separate problem, addressed by differential privacy rather than by MPC.
Example 18.26 (The millionaires' problem). Alice has (millions) and Bob has . They compute if and otherwise. What exactly does the security definition promise Alice?
Solution. The output is . In the ideal world, Bob's entire experience consists of his input and the bit . The definition requires a simulator that, given only , produces a transcript distributed identically to what Bob really sees.
Consequently Bob learns — this is implied by the bit itself and is unavoidable — but he does not learn , nor any bound better than : if he could, he could apply that same inference to the simulated transcript, which was generated without at all and therefore cannot distinguish from or .
Symmetrically, Alice learns only . Sanity check: run the function with instead; the output becomes , Bob learns , and again nothing more. The leakage is a property of , not of the protocol. □□
Not every function admits a perfectly secure protocol, and the obstruction appears already with two parties.
Theorem 18.27 (Two-party AND has no perfectly secure protocol). There is no protocol between two parties, secure against a single semi-honest corruption with unbounded computing power, that computes for input bits .
Proof. This is a sketch; it rests on a combinatorial analysis of protocol transcripts due to Chor and Kushilevitz. Consider the matrix of over the four input pairs. Perfect security forces the set of transcripts occurring on inputs to depend only on from Alice's side and only on from Bob's, which makes the transcript distribution a product structure; one shows that the set of input pairs producing a fixed transcript must be a combinatorial rectangle on which is constant, and that these rectangles can be merged, forcing to be decomposable into functions of alone and alone. The AND matrix admits no such decomposition. Hence the two-party case must rest on computational assumptions — which is exactly what Yao's protocol supplies, via oblivious transfer.∎
So the subject splits along a single fault line. With an honest majority, information-theoretic security is achievable for every function, and the tool is secret sharing (the section Information-Theoretic MPC with Secret Sharing (BGW)). Without one — in particular for two parties — cryptographic assumptions are necessary, and the tool is garbled circuits.
18.5Yao's Garbled Circuits for Two Parties
Yao's construction (1986) computes any function of two inputs, in the semi-honest model, with a constant number of rounds — the garbler sends one big message, the evaluator computes in silence. The function is presented as a Boolean circuit, and each wire is replaced by a pair of random keys.
The protocol needs one cryptographic primitive besides encryption.
Definition 18.28 (1-out-of-2 oblivious transfer). is the two-party functionality in which the sender inputs a pair , the receiver inputs a bit , and the receiver learns while
- the sender learns nothing about , and
- the receiver learns nothing about .
OT is precisely what is needed for the evaluator to obtain the key for its own input bit: the garbler must not learn which bit was requested, and the evaluator must not obtain both keys of a wire (holding both would let it evaluate the circuit on inputs it never had). By Two-party AND has no perfectly secure protocol, OT cannot be built unconditionally; it is constructed from trapdoor permutations or Diffie–Hellman.
Definition 18.29 (Garbling scheme). A garbling scheme for circuits is a triple of algorithms
- , producing a garbled circuit, a pair of keys per wire, and an output decoding map;
- ;
- , turning output keys into bits,
satisfying correctness — — and privacy: there is a simulator that, given only and the output , produces computationally indistinguishable from a real garbling.
Method 18.30 (Yao's protocol).
- Garble. For each wire the garbler draws independent random keys . For each gate with input wires and output wire it builds the four ciphertexts and permutes them randomly.
- Send. The garbler sends all garbled tables, the keys for its own input wires, and the output decoding map (key bit) for the output wires only.
- Transfer. For each of the evaluator's input wires the parties run one OT: sender input , receiver input its bit.
- Evaluate. Holding one key per input wire, the evaluator processes gates in topological order, decrypting the one row of each table that its two keys open, obtaining one key per internal wire.
- Decode. The evaluator maps the output keys to bits and sends the result to the garbler.
Intuition. Picture an encrypted maze. Every wire is a pair of keys and every gate is a padlocked box with four compartments, only one of which your two keys will open. You walk the maze holding exactly one key per wire, opening one compartment per gate, never learning whether the key in your hand means or — the two look alike. Only at the exit does the garbler hand you a legend for the final wires, and only then does anything become readable.
Theorem 18.31 (Security of Yao's protocol). If the encryption scheme is semantically secure (and has the mild property that a wrong-key decryption is detectably invalid) and the OT is secure, then Yao's protocol computes with computational security against a semi-honest adversary corrupting either party.
Proof. A sketch; it rests on the semantic security of the underlying encryption and on the security of OT, neither proved here.
Corrupt evaluator. By induction over the circuit in topological order, the evaluator holds exactly one key per wire and cannot tell which bit it represents, because the two keys of a wire are identically distributed random strings and the decoding map is released only for output wires. The simulator, given the output bits, garbles a fake circuit in which all four rows of every table encrypt the same output key, and rigs the output decoding map so that the resulting keys decode to the true output. A distinguisher between real and fake garbling yields a distinguisher against the encryption of the three rows the evaluator never opens, one hybrid gate at a time. The evaluator's OT messages are simulated by OT's receiver-privacy.
Corrupt garbler. The garbler receives no messages except the OT responses and the final output, so its view is simulated from its own input and using OT's sender-privacy.∎
Example 18.32 (Garbling a single AND gate). Write out the garbled table for one AND gate with input wires and output wire , and evaluate it on , .
Solution. The garbler draws six random -bit keys and forms, from the truth table of AND,
then shuffles the four rows so that position carries no information.
Evaluation with (the evaluator's own wire, via OT) and (sent by the garbler, whose bit is ): trying all four rows, exactly the second decrypts validly, yielding .
What has been learned: the evaluator holds , a random string, and never sees , so on an internal wire it cannot tell the value is . Sanity check: and the recovered key is ✓; also, had the evaluator been given both and it could have opened two rows and learned the garbler's input — which is exactly why step 3 uses OT and why the garbler sends only one key per input wire of its own. □□
Remark. Costs and the standard optimisations. A naive garbling sends ciphertexts per gate. Point-and-permute appends a random select bit to each key and uses the two select bits to index the row directly, removing the trial decryptions. Garbled row reduction fixes one ciphertext to zero and sends . Free-XOR chooses for a single global , after which an XOR gate needs no table and no communication at all — so only AND gates cost anything, and half-gates bring those to ciphertexts. An AES-128 circuit has about AND gates, so a garbled AES is a few hundred kilobytes, sent in one round.
Pitfall. A garbled circuit is single-use. Evaluating the same on two different inputs would give the evaluator two keys on some wire, which breaks the induction in the security proof and typically reveals the garbler's input. Each execution requires fresh garbling — and fresh OTs.
18.6Information-Theoretic MPC with Secret Sharing (BGW)
Now the two halves meet. BGW (Ben-Or, Goldwasser, Wigderson 1988) evaluates an arithmetic circuit over gate by gate while every intermediate value stays Shamir-shared, and it needs no computational assumption whatsoever.
Notation. The secret-sharing half wrote with reconstruction threshold and polynomial degree . MPC counts corruptions instead. Throughout this section is the number of corrupted parties, sharings use polynomials of degree at most , and reconstruction therefore needs shares. In the earlier notation: .
The choice of degree is forced from both sides. Degree is high enough that any colluding parties see points of a degree- polynomial and, by Shamir's scheme realises perfectly, learn nothing. It must not be higher, because reconstruction must still succeed from the honest parties.
Method 18.33 (The BGW protocol, semi-honest version).
- Input sharing. Each party Shamir-shares its input with a random polynomial of degree and sends one share to each party.
- Addition gate. Each party adds its two shares locally. No communication.
- Multiply-by-constant gate. Each party scales its share locally. No communication.
- Multiplication gate. Each party multiplies its two shares locally, then the parties run the degree-reduction subprotocol below.
- Output. The parties broadcast their shares of the output wire and interpolate.
Steps 2 and 3 are correct and private immediately by Shamir sharing is linear: sums and scalar multiples of degree- sharings are degree- sharings of the corresponding values, and a party that computes only on the shares it already holds sends nothing and hence leaks nothing.
Multiplication is where the work is. Let and be the degree- polynomials sharing and . Party can form locally, and the polynomial does satisfy . But is wrong as a sharing in two independent ways:
- Its degree is , so shares no longer determine it; reconstruction would need shares, and after a second multiplication the degree would be .
- It is not uniformly random among polynomials with the right constant term: is a product, hence reducible, and its coefficients are correlated. A coalition holding points of can extract information that points of a random polynomial would not reveal.
Intuition. The whole protocol is degree bookkeeping. A sharing is a polynomial and its degree is a budget: degree hides from people and needs to open. Addition spends nothing — adding two lines gives a line. Multiplication spends double, turning two lines into a parabola, and the budget must be paid back before the next gate. Degree reduction is the repayment, and it can only be afforded when there are at least people in the room.
The fix uses the one structural fact established in the first half: reconstruction is a fixed linear map. Spell it out.
Lemma 18.35 (Reconstruction of a degree- sharing is linear). Suppose and let have degree at most . With the recombination coefficients of Lagrange interpolation at for the points ,
and the are public constants, independent of .
Proof. has degree at most and points determine such a polynomial uniquely, so by Lagrange interpolation. Evaluate at and put , which depend only on the evaluation points.∎
Method 18.36 (Degree reduction (GRR re-sharing)). Each party holds , a share of under a degree- polynomial.
- Re-share. Party picks a fresh random polynomial of degree with and sends to every party .
- Recombine locally. Party computes
Theorem 18.37 (Degree reduction is correct and private). Let . Then and , so is a degree- Shamir sharing of . Moreover, if at most parties are corrupted, their shares are distributed exactly as shares of a uniformly random degree- sharing of , so they reveal nothing about , or .
Proof. Degree. Each has degree at most and is a fixed linear combination of them, so by Shamir sharing is linear.
Value. , the middle equality being Reconstruction of a degree- sharing is linear and the last with , .
Privacy. At least one index belongs to an honest party, because there are at most corrupted ones. Its polynomial is uniform among degree- polynomials with the prescribed constant term, independent of everything else, and (a Lagrange coefficient is a product of nonzero field elements). Write with the rest. Conditioned on all the adversary's other information, the non-constant coefficients of are uniform and independent, hence so are those of . Thus is a uniform degree- sharing of , and by the privacy half of Shamir's scheme realises perfectly its shares held by corrupted parties are uniform and independent of . The messages received from honest are, by the same theorem, uniform field elements.∎
Everything in that proof needed distinct honest-or-not evaluation points to exist, i.e. . This is the whole content of the famous threshold.
Corollary 18.38 (Honest majority: ). BGW evaluates any arithmetic circuit over with perfect security against a semi-honest adversary corrupting parties, provided , i.e. .
Proof. Input sharing, addition and scalar multiplication are perfectly private and correct by Shamir's scheme realises perfectly and Shamir sharing is linear; multiplication is by Degree reduction is correct and private, which requires . Every wire of the circuit therefore carries a uniform degree- sharing of its true value, and the adversary's view at every step consists of uniform field elements, which a simulator can sample without any input. Composing gate by gate, the whole view is simulatable from the corrupted inputs and the output.∎
Example 18.39 (Multiplying two shared values over ). Take , , . Let be shared by and by . Carry out one multiplication gate in full.
Solution. Shares held. , , ; , , .
Local products. , , . These lie on , a degree- polynomial with ✓.
Recombination coefficients for points (computed in the Shamir section): , , . Check: ✓ — the degree- sharing does reconstruct , but it took all three shares.
Re-sharing. Each party picks a random degree- polynomial with its as constant term: , , , and sends the evaluations
Local recombination. :
, , .
Verification. Interpolate , at : coefficients and , giving ✓. Sanity check: the new sharing is degree , since fits all three: , , ✓ — so any two parties now suffice, and a further multiplication can be performed. □□
Against a malicious adversary the threshold tightens, for a reason that is pure coding theory.
Proposition 18.40 (Malicious BGW needs without broadcast). The shares of a degree- polynomial form a Reed–Solomon code of length and dimension , whose minimum distance is . Correcting arbitrary corruptions requires , i.e. .
Proof. Two distinct degree- polynomials agree in at most places (their difference is a nonzero polynomial of degree ), so two distinct codewords differ in at least positions; and the bound is met by a polynomial with roots among the . A code corrects errors exactly when its minimum distance exceeds , since otherwise two codewords have a common word within distance and decoding is ambiguous. With this reads .∎
So with the honest parties can decode through the lies: a set of shares from which are arbitrarily wrong still determines the right polynomial, by Berlekamp–Welch. This is what makes the malicious version of BGW work with perfect security and guaranteed output delivery. If a broadcast channel is assumed instead, verifiable secret sharing plus zero-knowledge checks push the bound back to at the cost of a negligible error probability (Rabin–Ben-Or); it is the combination of no broadcast and no error that costs the factor three.
18.7Security Models and Feasibility
The results above hold in specific adversary models, and comparing protocols means fixing the model first. Four axes matter.
Definition 18.41 (Adversary models).
- Behaviour. A semi-honest (honest-but-curious, passive) adversary follows the protocol exactly and tries to infer extra information from its view. A malicious (Byzantine, active) adversary deviates arbitrarily: wrong messages, wrong inputs, early aborts.
- Corruption schedule. A static adversary fixes the corrupted set before the protocol starts; an adaptive one may corrupt further parties during the execution, based on what it has seen.
- Power. Computationally bounded (polynomial-time) or unbounded. Unbounded adversaries force information-theoretic protocols.
- Threshold. The maximum number of simultaneously corrupted parties, or more generally an adversary structure of tolerable corruption sets.
For malicious adversaries the semi-honest definition needs amendment, because a corrupt party may simply lie about its input, and no definition can prevent that — the ideal functionality accepts whatever input it is given. Security therefore compares the two worlds as whole executions.
Definition 18.42 (Real/ideal security against malicious adversaries). Let be the joint distribution of the adversary's output and the honest parties' outputs in an execution of , and let be the same for a simulator interacting with the ideal functionality (which may feed substituted inputs for the corrupted parties). The protocol securely computes if for every efficient adversary there is a simulator with
where is equality, statistical closeness, or computational indistinguishability according to the model.
Three properties are bundled into that single line, and it is worth naming them. Privacy: the simulator works from the ideal view only. Correctness: the honest parties' outputs in the ideal world are by definition of the substituted inputs, so the real protocol cannot make them output anything else. Input independence: the simulator must choose the substituted inputs before seeing the output, which rules out a corrupt party making its input depend on an honest one.
Remark. Security with abort. With a dishonest majority one weakens the ideal world: the adversary receives first and may then tell the functionality whether to deliver to the honest parties or the symbol . This is not a blemish to be polished away — the next theorem says it is unavoidable.
Intuition. Why is fairness the first casualty of a dishonest majority? Whoever speaks last in a protocol sees the answer a moment before everyone else, and nothing but an honest majority can force them to pass it on. With a majority of honest parties the others can finish the computation without the deserter; without one, the deserter holds the only remaining copy. That single asymmetry is what Cleve's theorem turns into a quantitative bound.
Theorem 18.43 (Cleve: fair coin-tossing is impossible with a dishonest majority). There is no two-party protocol for tossing an unbiased coin that is secure against a malicious party who may abort: for every -round protocol some party has a strategy biasing the honest party's output by .
Proof. A sketch of Cleve's argument. Let be the value the honest party would output if the other aborted after round ; is a fixed default and is the true output, so the expectations run from a constant to . Along the sequence some consecutive pair differs by at least in absolute value, and the party who moves at that round can, by choosing between aborting and continuing, force the output towards whichever side it prefers. Hence perfect fairness is unattainable, and with it guaranteed output delivery.∎
Corollary 18.44 (The feasibility map).
- , semi-honest or malicious, dishonest majority: possible with computational assumptions (Yao + OT; GMW), with abort. Not possible information-theoretically, by Two-party AND has no perfectly secure protocol.
- , semi-honest, unbounded adversary: perfect security for every function, by Honest majority: .
- , malicious, unbounded, no broadcast: perfect security with guaranteed output delivery (BGW), by Malicious BGW needs without broadcast.
- , malicious, unbounded, with broadcast: statistical security with guaranteed output delivery (Rabin–Ben-Or), using VSS.
- , malicious: computational assumptions and security with abort (GMW, SPDZ); fairness impossible by Cleve: fair coin-tossing is impossible with a dishonest majority.
The route from the weakest model to the strongest is a compiler rather than a new protocol.
Example 18.45 (The GMW compiler). How does one turn a protocol secure against semi-honest adversaries into one secure against malicious adversaries?
Solution. Commit. Each party commits to its input and to its random tape at the outset, so neither can be changed later. The random tape is generated jointly (a coin-tossing-into-the-well subprotocol) so that a corrupt party cannot choose biased randomness.
Observe that messages are deterministic. In any fixed protocol the next message is a public function of committed data and public data.
Prove each message. Along with , the party sends a zero-knowledge proof of the statement "there exist opening my commitments for which ". The proof reveals nothing beyond the truth of that statement.
Effect. Any deviation produces a false statement and is rejected, so a malicious party is restricted to semi-honest behaviour with a possibly substituted input — precisely what the ideal world already permits. Sanity check: privacy is preserved because zero-knowledge proofs are simulatable, and the compiled protocol's simulator runs the semi-honest simulator plus the ZK simulators. The cost is the price of malicious security: a zero-knowledge proof per message, which is why practical protocols instead use cut-and-choose or information-theoretic MACs (SPDZ). □□
Remark. Preprocessing. Modern protocols split into a slow, input-independent offline phase and a fast online one. Beaver triples are the canonical example: shared random with , prepared in advance. To multiply shared and online, the parties open and — safe, because are uniform and independent one-time pads — and compute
using only the linear operations of Shamir sharing is linear. The online phase is then two openings per multiplication, with no cryptography at all.
Remark. Composition. A protocol proved secure standalone need not stay secure when many copies run concurrently inside a larger system. The universal composability framework quantifies over an environment that interacts with the protocol and the adversary throughout, and its composition theorem states that a UC-secure subprotocol may be substituted for its ideal functionality anywhere without loss. UC security is strictly stronger and, for most functionalities, unachievable without setup assumptions such as a common reference string.
Pitfall. Two thresholds are easy to confuse. The secret-sharing threshold says how many shares reconstruct; the corruption threshold says how many parties the adversary controls. BGW ties them by , so a statement like " -out-of- sharing tolerates corruptions" is doubly wrong: it tolerates , and is exactly why the protocol works.
- Reading the evaluation points as the secret data. In Shamir's scheme the are public identifiers; the secrets are the values . Publishing an index is harmless, publishing a value is not.
- **Believing shares give "partial" information.** In a perfect scheme they give exactly zero: by *Shamir's scheme realises perfectly* the posterior on equals the prior, however much computing power you have.
- **Working over for composite . ** Interpolation divides by , which need not be invertible outside a field. is not a field, and the scheme built over it is not a threshold scheme.
- Sharing a long secret in a small field. Shamir shares one field element. A long secret must be split into blocks shared with *independent* polynomials, or a larger field used; reusing one polynomial across blocks correlates them.
- Trusting the dealer. A corrupt dealer can distribute inconsistent points so that different qualified sets reconstruct different values. That is what verifiable secret sharing exists to prevent, and Feldman's check is the cheapest fix.
- Equating computational and information-theoretic sharing. Computational schemes achieve shares shorter than the secret, which *Share size lower bound* forbids in the perfect setting; they do so by assuming an adversary that cannot break an encryption.
- Assuming MPC needs a trusted party. The trusted party is a *definitional device*: the ideal world exists to say what security means. The protocol's entire purpose is to emulate it with no such party present.
- Believing the output leaks nothing. MPC protects inputs only beyond what implies. If is the sum, the sum becomes public — and colluding parties recover the last input by subtraction.
- Expecting information-theoretic security with a dishonest majority. It is impossible already for the AND of two bits. Dishonest-majority MPC is necessarily computational and necessarily allows abort.
- Confusing Yao with BGW. Yao is two-party, constant-round, computational, and rests on OT; BGW is -party, round complexity proportional to circuit *depth*, information-theoretic, and rests on an honest majority.
- Forgetting the degree blow-up. Multiplying shares locally is correct but doubles the degree and destroys uniformity. Without the re-sharing step the second multiplication of a circuit is unreconstructable.
- Underestimating the cost of malicious security. Semi-honest protocols are typically linear in circuit size; malicious security adds zero-knowledge proofs, cut-and-choose, or authenticated triples — practical today, but never free.