Multiparty computation secure against continual memory leakage
From MaRDI portal
Recommendations
- Leakage-tolerant computation with input-independent preprocessing
- On-line/off-line leakage resilient secure computation protocols
- Proactive secure multiparty computation with a dishonest majority
- Secure computation against adaptive auxiliary information
- Multi-Party Computation with Omnipresent Adversary
Cited in
(23)- Provably secure certificate-based encryption with leakage resilience
- Leakage resilient one-way functions: the auxiliary-input setting
- Mode-level vs. implementation-level physical security in symmetric cryptography. A practical guide through the leakage-resistance jungle
- Constant-round leakage-resilient zero-knowledge from collision resistance
- Leakage-resilient coin tossing
- Continuous leakage-resilient certificate-based encryption
- Enabling cloud storage auditing with key-exposure resilience under continual key-leakage
- Leakage-resilient functional encryption via pair encodings
- Deterministic Public-Key Encryption Under Continual Leakage
- Secure computation against adaptive auxiliary information
- Leakage-tolerant computation with input-independent preprocessing
- On-line/off-line leakage resilient secure computation protocols
- Leakage Resilient One-Way Functions: The Auxiliary-Input Setting
- Constant-round leakage-resilient zero-knowledge argument for NP from the knowledge-of-exponent assumption
- Secure Multi-party Computation: Information Flow of Outputs and Game Theory
- How to Compute in the Presence of Leakage
- Memory leakage-resilient secret sharing schemes
- Unconditionally secure computation against low-complexity leakage
- Correction to: ``Unconditionally secure computation against low-complexity leakage
- Protecting distributed primitives against leakage: equivocal secret sharing and more
- NIZK amplification via leakage-resilient secure computation
- LR-OT: leakage-resilient oblivious transfer
- Fully leakage-resilient signatures revisited: graceful degradation, noisy leakage, and construction in the bounded-retrieval model
This page was built for publication: Multiparty computation secure against continual memory leakage
Report a bug (only for logged in users!)Click here to report a bug for this page (MaRDI item Q5415547)