Efficient Refreshing Protocol for Leakage-Resilient Storage Based on the Inner-Product Extractor
Marcin Andrychowicz

TL;DR
This paper introduces a more efficient and simpler protocol for refreshing leakage-resilient storage in cryptographic systems, reducing the refresh operation complexity from quadratic to linear in the security parameter.
Contribution
The authors present a novel leakage-resilient storage refresh protocol that is both simpler and more efficient, requiring only linear operations compared to previous quadratic methods.
Findings
Reduces refresh complexity from Ω(n^2) to O(n) operations
Maintains security assumptions of independent leakage and bounded observations
Simplifies implementation of leakage-resilient cryptographic protocols
Abstract
A recent trend in cryptography is to protect data and computation against various side-channel attacks. Dziembowski and Faust (TCC 2012) have proposed a general way to protect arbitrary circuits against any continual leakage assuming that: (i) the memory is divided into the parts, which leaks independently (ii) the leakage in each observation is bounded (iii) the circuit has an access to a leak-free component, which samples random orthogonal vectors. The pivotal element of their construction is a protocol for refreshing the so-called Leakage-Resilient Storage (LRS). In this note, we present a more efficient and simpler protocol for refreshing LRS under the same assumptions. Our solution needs O(n) operations to fully refresh the secret (in comparison to {\Omega}(n^2) for a protocol of Dziembowski and Faust), where n is a security parameter that describes the maximal amount of leakage…
Peer Reviews
No public reviews on file for this paper yet. If you reviewed it on a platform where reviews are public (OpenReview, ICLR, NeurIPS, ICML), you can paste yours below so the community can read it here.
Videos
No videos yet. Explain this paper in a talk, walkthrough, or lecture? Add one.
Taxonomy
TopicsCryptography and Data Security · Cryptographic Implementations and Security · Physical Unclonable Functions (PUFs) and Hardware Security
