Crates.io | opaque-ke |
lib.rs | opaque-ke |
version | 3.0.0 |
source | src |
created_at | 2020-05-28 19:16:01.042192 |
updated_at | 2024-10-10 05:25:01.270672 |
description | An implementation of the OPAQUE password-authenticated key exchange protocol |
homepage | |
repository | https://github.com/facebook/opaque-ke |
max_upload_size | |
id | 247126 |
size | 619,729 |
OPAQUE is an augmented password-authenticated key exchange protocol. It allows a client to authenticate to a server using a password, without ever having to expose the plaintext password to the server.
This implementation is based on the Internet Draft for OPAQUE.
Augmented Password Authenticated Key Exchange (aPAKE) protocols are designed to provide password authentication and mutually authenticated key exchange without relying on PKI (except during user/password registration) and without disclosing passwords to servers or other entities other than the client machine.
OPAQUE is a PKI-free aPAKE that is secure against pre-computation attacks and capable of using a secret salt.
The API can be found here along with an example for usage. More examples can be found in the examples directory.
Add the following line to the dependencies of your Cargo.toml
:
opaque-ke = "3"
Rust 1.74 or higher.
This library was audited by NCC Group in June of 2021. The audit was sponsored by WhatsApp for its use in enabling end-to-end encrypted backups.
The audit found issues in release v0.5.0
, and the fixes were subsequently incorporated into release v1.2.0
. See the full audit report here.
@serenity-kit/opaque
and opaque-wasm
can be found here@serenity-kit/opaque
The authors of this code are Kevin Lewi (@kevinlewi) and François Garillot (@huitseeker). To learn more about contributing to this project, see this document.
Special thanks go to Hugo Krawczyk and Chris Wood for helping to clarify discrepancies and making suggestions for improving this implementation. Additional credit goes to @daxpedda for adding no_std support, p256 support, and making other general improvements to the library.
This project is dual-licensed under either the MIT license or the Apache License, Version 2.0. You may select, at your option, one of the above-listed licenses.