Runzhi Zeng

dblp:272/0960 · DBLP profile ↗
← Back
8ranked-venue papers
1as first author
7since 2021 · last 2026
0000-0002-8606-3007ORCID · corroborated

Domains — the database's venue-derived domains; a paper can count in several

Security and privacy · 8 · 1 first-author · 7 since 2021
YearPublicationVenuePosition
2026 Generic Constructions of Compact and Tightly Selective-Opening Secure Public-Key Encryption Schemes
Jiaxin Pan 0001, Benedikt Wagner, Runzhi Zeng
J. Cryptol.3
2025 sfXHMQV: Better Efficiency and Stronger Security for Signal's Initial Handshake based on HMQV
Rune Fiedler, Felix Günther 0001, Jiaxin Pan 0001, Runzhi Zeng
CRYPTO (8)4
2024 Key Exchange with Tight (Full) Forward Secrecy via Key Confirmation
Jiaxin Pan 0001, Doreen Riepel, Runzhi Zeng
EUROCRYPT (6)3
2023 Tighter Security for Generic Authenticated Key Exchange in the QROM
Jiaxin Pan 0001, Benedikt Wagner, Runzhi Zeng
ASIACRYPT (4)3
2023 A Generic Construction of Tightly Secure Password-Based Authenticated Key Exchange
Jiaxin Pan 0001, Runzhi Zeng
ASIACRYPT (8)2
2023 Lattice-Based Authenticated Key Exchange with Tight Security
Jiaxin Pan 0001, Benedikt Wagner, Runzhi Zeng
CRYPTO (5)3
2022 Compact and Tightly Selective-Opening Secure Public-key Encryption Schemes
Jiaxin Pan 0001, Runzhi Zeng
ASIACRYPT (3)2
2020 Tightly-secure two-pass authenticated key exchange protocol using twin Diffie-Hellman problem
abstract
Tight security is an important requirement of practical cryptographic schemes. Compared with loosely‐secure schemes, tightly‐secure schemes allow shorter security parameters hence are more efficient. In CRYPTO 2018, Gjøsteen and Jager proposed a tightly‐secure authenticated key exchange (AKE) protocol. They used ‘commitment trick’ to construct a tight security reduction for their protocol. However, this technique leads to a three‐pass execution in their protocol, and their protocol cannot achieve key confirmation unless it is modified to have a four‐pass execution. In this study, the authors propose a tightly‐secure two‐pass AKE protocol. They use the twin Diffie–Hellman problem and the ‘re‐patch’ trick of random oracles to construct a tight security reduction for their protocol. This technique allows their protocol to have a two‐pass execution. Their protocol provides several security properties such as key‐compromise‐impersonation security, unknown‐key‐share security, and weak perfect forward secrecy. Moreover, a three‐pass variant of their protocol provides key confirmation.
Runzhi Zeng
IET Inf. Secur.1