Struct wow_srp::client::SrpClientUser

pub struct SrpClientUser { /* fields omitted */ }

Starting point of the client. Next step is SrpClientChallenge.

Uses NormalizedStrings for the reasons described there.

All arrays are little endian.

Implementations

impl SrpClientUser

pub fn new(username: NormalizedString, password: NormalizedString) -> Self

Creates a new SrpClientUser from username and password.

NormalizedString is used for the reasons described there.

pub fn into_challenge(
    self,
    generator: u8,
    large_safe_prime: [u8; 32],
    server_public_key: PublicKey,
    salt: [u8; 32]
) -> SrpClientChallenge

Takes the server supplied variables and computes the next step.

The generator and large safe prime are not checked for validity.

All arrays are little endian.

Panics

Panics on the extremely unlikely chance that the generated public key is invalid. See PublicKey for details on validity.

There are only two invalid states for the randomly generated server public key:

• All zeros.
• Exactly the same as the large safe prime.

This is 2 out of 2^256 possible states. The chances of this occurring naturally are very slim. It is significantly more likely that the RNG of the system has been compromised in which case authentication is not possible.