A SASL and GSS-API Mechanism using the asymmetric password-authenticated key agreement OPAQUE
draft-reitzenstein-kitten-opaque-02
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Author | Nadja von Reitzenstein Čerpnjak | ||
Last updated | 2023-07-25 (Latest revision 2023-01-16) | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Additional resources |
GitHub Repository
|
||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Expired | |
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This specification describes a Simple Authentication and Security Layer (SASL, RFC4422) authentication mechanisms based on the OPAQUE asymmetric password-authenticated key agreement (PAKE) protocol. The mechanism offers two distinct advantages over the SCRAM family of mechanisms. The underlying OPAQUE protocol provides the ability for clients to register without the server having to have access to the clear text password of an user, preventing password exfiltration at registration. Secondly a successful authentication produces a long- term secret key specific to the user that can be used to access encrypted server-side data without needing to share keys between clients via side-band mechanisms. When used in combination with TLS or an equivalent security layer these mechanisms allow for secure channel binding.
Authors
Nadja von Reitzenstein Čerpnjak
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)