Security weakness in a three-party pairing-based protocol for password authenticated key exchange
DOI10.1016/J.INS.2006.09.001zbMATH Open1125.94037OpenAlexW2048985559WikidataQ114666934 ScholiaQ114666934MaRDI QIDQ865906FDOQ865906
Authors: Junghyun Nam, Seungjoo Kim, Dongho Won, Young-Sook Lee
Publication date: 20 February 2007
Published in: Information Sciences (Search for Journal in Brave)
Full work available at URL: https://doi.org/10.1016/j.ins.2006.09.001
Recommendations
- Finding and fixing vulnerabilities in several three-party password authenticated key exchange protocols without server public keys
- Three weaknesses in a simple three-party key exchange protocol
- Provably secure three-party password-based authenticated key exchange protocol using Weil pairing
- Cryptology and Network Security
- Public Key Cryptography - PKC 2005
man-in-the-middle attackprovable securityWeil pairingkey exchange protocolpassword-based authentication
Cites Work
- Provably secure three-party password-based authenticated key exchange protocol using Weil pairing
- Title not available (Why is that?)
- Title not available (Why is that?)
- Identity-Based Encryption from the Weil Pairing
- Title not available (Why is that?)
- Authenticated key exchange secure against dictionary attacks
- Title not available (Why is that?)
- Title not available (Why is that?)
- Protocols for authentification and key establishment
- Title not available (Why is that?)
- Advances in Cryptology - CRYPTO 2003
- Selected Areas in Cryptography
- Identity-based authenticated key agreement protocol based on Weil pairing
- Topics in Cryptology – CT-RSA 2005
- Cryptography and Coding
- Public Key Cryptography - PKC 2005
- Financial Cryptography and Data Security
- Cryptanalysis of tripartite and multi-party authenticated key agreement protocols
- A one round protocol for tripartite Diffie-Hellman
- Errors in Computational Complexity Proofs for Protocols
- Examining Indistinguishability-Based Proof Models for Key Establishment Protocols
- Security in Communication Networks
- New Approaches to Password Authenticated Key Exchange Based on RSA
Cited In (21)
- EC2C-PAKA: an efficient client-to-client password-authenticated key agreement
- Robust biometric-based three-party authenticated key establishment protocols
- Development of a new cryptographic construct using palmprint-based fuzzy vault
- Secure threshold multi authority attribute based encryption without a central authority
- On password-based authenticated key exchange using collisionful hash functions
- Weakness in a RSA-based password authenticated key exchange protocol
- Resource-aware protocols for authenticated group key exchange in integrated wired and wireless networks
- Cryptanalysis of simple three-party key exchange protocol (S-3PAKE)
- Provably secure three-party password-based authenticated key exchange protocol
- A countable and time-bound password-based user authentication scheme for the applications of electronic commerce
- Hybrid proxy multisignature: a new type multi-party signature
- Cryptanalysis of a simple three-party key exchange protocol
- Finding and fixing vulnerabilities in several three-party password authenticated key exchange protocols without server public keys
- On the security analysis of Lee, Hwang and Lee (2004) and Song and Kim (2000) key exchange/agreement protocols
- A security weakness in Abdalla et al.'s generic construction of a group key exchange protocol
- Three weaknesses in a simple three-party key exchange protocol
- Applied Cryptography and Network Security
- Provably secure three-party password-based authenticated key exchange protocol using Weil pairing
- Provably secure and efficient identification and key agreement protocol with user anonymity
- Cryptology and Network Security
- Provably secure three party encrypted key exchange scheme with explicit authentication
Uses Software
This page was built for publication: Security weakness in a three-party pairing-based protocol for password authenticated key exchange
Report a bug (only for logged in users!)Click here to report a bug for this page (MaRDI item Q865906)