Bounded tamper resilience: how to go beyond the algebraic barrier
From MaRDI portal
Publication:2867150
Recommendations
- Bounded tamper resilience: how to go beyond the algebraic barrier
- Cryptography secure against related-key attacks and tampering
- Efficient public-key cryptography with bounded leakage and tamper resilience
- Continuous non-malleable key derivation and its application to related-key security
- Related-key secure key encapsulation from extended computational bilinear Diffie-Hellman
Cited in
(20)- Continuously non-malleable codes in the split-state model
- Locally decodable and updatable non-malleable codes and their applications
- Subversion-resilient signatures: definitions, constructions and applications
- Tamper and Leakage Resilience in the Split-State Model
- Algorithmic Tamper-Proof Security under Probing Attacks
- Efficient public-key cryptography with bounded leakage and tamper resilience
- Fully leakage-resilient signatures revisited: graceful degradation, noisy leakage, and construction in the bounded-retrieval model
- Super-strong RKA secure MAC, PKE and SE from tag-based hash proof system
- Anonymous and leakage resilient IBE and IPE
- More efficient public-key cryptography with leakage and tamper resilience
- Witness maps and applications
- Continuously non-malleable codes with split-state refresh
- Public-key encryption for protecting data in cloud system with intelligent agents against side-channel attacks
- Public key encryption resilient to leakage and tampering attacks
- Practical non-malleable codes from symmetric-key primitives in 2-split-state model
- The Chaining Lemma and its application
- Public-Key Cryptosystems Resilient to Continuous Tampering and Leakage of Arbitrary Functions
- NIZK from SNARGs
- Bounded tamper resilience: how to go beyond the algebraic barrier
- Non-malleable Codes with Split-State Refresh
This page was built for publication: Bounded tamper resilience: how to go beyond the algebraic barrier
Report a bug (only for logged in users!)Click here to report a bug for this page (MaRDI item Q2867150)