>The same happens with PAKE during registration, where the user will need to provide the verifier. In a typical PAKE, generated challenge depends on random val

>The same happens with PAKE during registration, where the user will need to provide the verifier. In a typical PAKE, generated challenge depends on random values generated by both server and user, so if at least one of them is not controlled by an attacker, the generated challenge will be different each time. So leaking the verifier or eavesdropping on previous logins does not help an attacker to impersonate user in any way.