Password-Authenticated Key (PAK) Diffie-Hellman Exchange
RFC 5683
Revision differences
Document history
Date | By | Action |
---|---|---|
2021-04-06
|
(System) | Received changes through RFC Editor sync (added Errata tag, added Verified Errata tag) |
2018-12-20
|
(System) | Received changes through RFC Editor sync (changed abstract to 'This document proposes to add mutual authentication, based on a human-memorizable password, to the basic, unauthenticated … Received changes through RFC Editor sync (changed abstract to 'This document proposes to add mutual authentication, based on a human-memorizable password, to the basic, unauthenticated Diffie-Hellman key exchange. The proposed algorithm is called the Password-Authenticated Key (PAK) exchange. PAK allows two parties to authenticate themselves while performing the Diffie-Hellman exchange. The protocol is secure against all passive and active attacks. In particular, it does not allow either type of attacker to obtain any information that would enable an offline dictionary attack on the password. PAK provides Forward Secrecy. This document is not an Internet Standards Track specification; it is published for informational purposes.') |
2015-10-14
|
(System) | Notify list changed from abrusilovsky@lucent.com, draft-brusilovsky-pak@ietf.org, rfc-editor@rfc-editor.org to rfc-editor@rfc-editor.org |
2010-03-13
|
(System) | Posted related IPR disclosure: Alcatel-Lucent's Statement about IPR related to RFC 5683 and draft-brusilovsky-pak-11 |
2010-02-09
|
Amy Vezza | State Changes to RFC Published from RFC Ed Queue by Amy Vezza |
2010-02-09
|
Amy Vezza | [Note]: 'RFC 5683' added by Amy Vezza |
2010-02-08
|
(System) | RFC published |