RFC 8146: Adding Support for Salted Password Databases to EAP-pwd
In plain English — editorial summary, not part of the RFC
EAP-pwd is an Extensible Authentication Protocol (EAP) method that utilizes a shared password for authentication using a technique that is resistant to dictionary attacks. It includes support for raw keys and double hashing of a password in the style of Microsoft Challenge Handshake Authentication Protocol version 2 (MSCHAPv2), but it does not include support for salted passwords. There are many existing databases of salted passwords, and it is desirable to allow their use with EAP-pwd.
Document record
- Document ID
- RFC8146
- Published
- April 2017
- Authors
- D. Harkins
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- —
- Pages
- 11
- Also known as
- —
- Updates:
- RFC 5931
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7664Dragonfly Key ExchangeCurrent
November 2015
- RFC 6628Efficient Augmented Password-Only Authentication and Key Exchange for IKEv2Current
June 2012
- RFC 6617Secure Pre-Shared Key (PSK) Authentication for the Internet Key Exchange Protocol (IKE)Current
June 2012
- RFC 8492Secure Password Ciphersuites for Transport Layer Security (TLS)Current
February 2019
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?