Find
C
ase-sensitive
R
egexp search
Path
Showing
f5d7cc82
from
2026-11-19
:
No bug - Use consistent formatting in a components.conf file. rs=me
comm-central
/
third_party
/
botan
/
src
/
lib
/
pake
/
spake2p
Navigation
Enable keyboard shortcuts
Name
Description
Size
Coverage
info.txt
273
-
spake2p.cpp
RFC 9383 Section 3.2 w0s || w1s = PBKDF(len(pw) || pw || len(idProver) || idProver || len(idVerifier) || idVerifier) w0 = w0s mod p w1 = w1s mod p
18187
-
spake2p.h
SPAKE2+ (RFC 9383) password authenticated key exchange SPAKE2+ is an augmented PAKE; the two sides are asymmetric. The prover knows the password itself, while the verifier stores only a registration record derived from the password. An attacker who steals the registration record cannot impersonate the prover without first performing a dictionary attack on the record. The expected message flow is - The prover calls ProverContext::generate_message and sends the result (shareP) to the verifier. - The verifier calls VerifierContext::process_message and sends the result (shareV followed by confirmV) to the prover. - The prover calls ProverContext::process_message, which checks the verifier's key confirmation, and sends the result (confirmP) to the verifier. - The verifier calls VerifierContext::verify_confirmation After the final confirmation step both sides can call shared_secret to obtain the session key (K_shared in RFC 9383) Protocols which embed SPAKE2+ and perform the prover's key confirmation themselves (such as the proposed TLS PAKE extension) may instead call VerifierContext::skip_confirmation in place of the final step.
14994
-