GARBLED CIRCUITS CHECKING GARBLED CIRCUITS MORE EFFICIENT AND SECURE TWO-PARTY COMPUTATION Payman Mohassel Ben Riva University of Calgary Tel Aviv University
Secure Two-Party Computation Privacy: Only learn the output Correctness: Learn the intended function
Contributions 2PC with low overhead Input–consistency check Two-output functions New Definition Strengthen covert adversaries Better efficiency/security trade-off for practice Protocols meeting the definition
Garbled Circuit seed Eval() 4
Useful Properties 5
Malicious 2PC Cut-and-Choose Open Evaluate Majority Are all inputs the same? Is the output correct? Question
1) Is the output correct? Open Evaluate Majority Send GOs as proof
2) Is the output correct? Open Evaluate Majority Use same output labels in all circuits
3) Is the output correct? Open Evaluate Majority
Extensions
Covert 2PC What about cost/pay for honest party? Question cost/pay for malicious party
All-or-Nothing Security
A Stronger Definition Increase the pay-off (of learning correct output) Orthogonal to MPC Reduce the cost of being cheated on! By strengthening the security definition
CovIDA Security
Dual-Ex 2PC Yes/no o Correctness prob. = 1-neg(k) o Leakage prob. = 1 o Bad circuit o Different inputs
Dual-Ex + Covert 2PC Yes/no o Correctness prob. = 1-neg(k) o Leakage prob. = 1 o Bad circuit o Different inputs
Dual-Ex + Covert 2PC
Are inputs the Same? Malicious 2PC Use same OT for x Linear in s symmetric-key Ops for input-consistency (using OT extension)
QUESTIONS?