Posted in Identity and Access Management

RFC 9807: The OPAQUE Augmented Password-Authenticated Key Exchange (aPAKE) Protocol

Gheorghe B. — Senior Software Engineer

A password manager solves password reuse. It doesn’t change what happens when you log in: in a conventional password flow, TLS protects the connection, but the server still receives the password before checking it.

At Cyberr we’re exploring OPAQUE, an augmented password-authenticated key exchange (aPAKE). Instead of sending the password to the server, the client and server run a protocol that authenticates the user and establishes a shared session key.

The interesting part is the breach model. OPAQUE uses an oblivious pseudorandom function and a key-stretching function to protect the registration record. An attacker who steals the server’s credentials still faces offline guessing, but can’t precompute the useful password-mapping work before the compromise.

This isn’t a replacement for a password manager, phishing-resistant MFA, or a sound implementation. It’s another layer: even a strong, unique password is worth keeping out of the server’s hands.

https://www.rfc-editor.org/rfc/rfc9807.html

RFC 9807: The OPAQUE Augmented Password-Authenticated Key Exchange (aPAKE) Protocol

4 reactions · 0 comments

Read and join the discussion on Cyberr