Security
Big Secrets Small Shares: Revisiting Secure Multi-Party Computation
arXiv cs.CR0 views
arXiv:2610.27609v1 Announce Type: new Abstract: At CRYPTO 2007, Damg{\aa}rd and Nielsen introduced a preprocessing approach to multi-party computation (MPC) to achieve linear communication complexity. Another approach to reduce communication complexity was proposed by Cramer, Damg{\aa}rd, and de Haan at EUROCRYPT 2007, which involved using ramp-secret sharing schemes to jointly share base-field components of secrets from the extension field. In this paper, we combine these two ideas to achieve a non-asymptotic reduction of communication cost in a multi-phase MPC setup. We introduce a new modification of the ramp secret sharing scheme, called compact sharing, and tailor the MPC protocol to accommodate this modification. Compact sharing masks the polynomial coefficients that would otherwise leak during degree reduction. The protocol provides perfect security against static semi-honest adversaries under an explicit tradeoff between the corruption threshold and the extension degree. When the extension degree scales linearly with the number of parties, the gate-evaluation core achieves constant communication overhead relative to an extension-field element, amortized over full preprocessing batches; input and output communication is counted separately.
Source:https://arxiv.org/abs/2610.27609PreviousKNOX: Hardware-assisted Regulatory Sandbox for Generative ModelsNextDISTA-LP: Privacy-Preserving Distributed Linear Programming for Metric Differential Privacy
Related posts

Connecting AWS to Another Network with a Site-to-Site VPN
0dev.to AWS
CVE-2026-28328 and the Limits of Product-Fingerprint Exposure Data
0dev.to Security
Self-Employed? Solopreneur? NIST Has a Cybersecurity Guide Just for You
0Hacker News New
Apple’s HomeView may double as security camera – watch out Ring, Nest, and Wyze
0ZDNet
Future-proof security system protects Bitcoin Lightning Network from quantum attacks
0Phys.org Tech
CVE-2026-106074: a build-time randomness leak in Node.js snapshots
0dev.to Node