RFC 5931: Extensible Authentication Protocol (EAP) Authentication Using Only a Password
In plain English — editorial summary, not part of the RFC
This memo describes an Extensible Authentication Protocol (EAP) method, EAP-pwd, which uses a shared password for authentication. The password may be a low-entropy one and may be drawn from some set of possible passwords, like a dictionary, which is available to an attacker. The underlying key exchange is resistant to active attack, passive attack, and dictionary attack. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC5931
- Published
- August 2010
- Authors
- D. Harkins; G. Zorn
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- —
- Pages
- 40
- Also known as
- —
- Updated by:
- RFC 8146
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8492Secure Password Ciphersuites for Transport Layer Security (TLS)Current
February 2019
- RFC 6124An EAP Authentication Method Based on the Encrypted Key Exchange (EKE) ProtocolCurrent
February 2011
- RFC 6617Secure Pre-Shared Key (PSK) Authentication for the Internet Key Exchange Protocol (IKE)Current
June 2012
- RFC 7664Dragonfly Key ExchangeCurrent
November 2015
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?