Adding Support for Salted Password Databases to EAP-pwd
RFC 8146
Revision differences
Document history
Date | By | Action |
---|---|---|
2020-01-21
|
(System) | Received changes through RFC Editor sync (added Verified Errata tag) |
2018-08-10
|
(System) | Received changes through RFC Editor sync (added Errata tag) |
2017-04-21
|
(System) | Received changes through RFC Editor sync (created alias RFC 8146, changed abstract to 'EAP-pwd is an Extensible Authentication Protocol (EAP) method that utilizes a … Received changes through RFC Editor sync (created alias RFC 8146, changed abstract to '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.', changed pages to 11, changed standardization level to Informational, changed state to RFC, added RFC published event at 2017-04-21, changed IESG state to RFC Published, created updates relation between draft-harkins-salted-eap-pwd and RFC 5931) |
2017-04-21
|
(System) | RFC published |