All Projects → jedisct1 → rust-cpace

jedisct1 / rust-cpace

Licence: other
A Rust implementation of CPace, a balanced PAKE.

Programming Languages

rust
11053 projects

Projects that are alternatives of or similar to rust-cpace

spake2-ee
A SPAKE2+ Elligator Edition implementation for libsodium 1.0.16+
Stars: ✭ 36 (+100%)
Mutual labels:  pake
pake
PAKE library for generating a strong secret between parties over an insecure channel
Stars: ✭ 163 (+805.56%)
Mutual labels:  pake
Croc
Easily and securely send things from one computer to another 🐊 📦
Stars: ✭ 17,834 (+98977.78%)
Mutual labels:  pake
pqcrypto
👻 Post-quantum cryptography for Python.
Stars: ✭ 15 (-16.67%)
Mutual labels:  key-exchange

Documentation

CPace-Ristretto255, a balanced PAKE

A CPace implementation for Rust.

This is a port of the CPace implementation for libsodium.

Blurb

CPace is a protocol for two parties that share a low-entropy secret (password) to derive a strong shared key without disclosing the secret to offline dictionary attacks.

CPace is a balanced PAKE, meaning that both parties must know the low-entropy secret.

Applications include pairing IoT and mobile applications using ephemeral pin codes, QR-codes, serial numbers, etc.

Usage

The CPace protocol requires a single round trip.

It returns a set of two 256-bit (SHARED_KEY_BYTES bytes) keys that can be used to communicate in both directions.

use pake_cpace::CPace;

// client-side
let client = CPace::step1("password", "client", "server", Some("ad")).unwrap();

// server-side
let step2 = CPace::step2(&client.packet(), "password", "client", "server", Some("ad")).unwrap();

// client-side
let shared_keys = client.step3(&step2.packet()).unwrap();

// both parties now have the same set of shared keys
assert_eq!(shared_keys.k1, step2.shared_keys().k1);
assert_eq!(shared_keys.k2, step2.shared_keys().k2);

Notes

  • This implementation uses the Ristretto255 group and SHA-512 as the hash function, so it is compatible with the C implementation and can trivially be ported to wasm-crypto.
  • Client and server identifiers have a maximum size of 255 bytes.
  • no_std compatible, WebAssembly compatible.
Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].