fix(auth)!: the first authenticator takes the password, and a reset ends every session
The fourth reading's second finding: a stolen session outlived the reset of the authenticators (carrying it out ended no session) and confirmed the account's first authenticator on its own code alone, ahead of the owner, so the owner's confirmation and sign-in were refused after. - Carrying out a reset of the authenticators ends every session of the account, on the register at once and on every member by notice, as the other resets do; the sign-in that carries it out gets its session after that moment (PasswordProof.sessionsEndedBefore, issueSessionAfter). - Confirming the first authenticator takes the password's proof for a change's challenge, without a code (proveOwnersPassword), counted per session as the owner's proofs are: a session of a lost phone, or of a setup never finished, claims no second factor. The app sends the password with every confirmation: the sign-up's, a reset's and the account section's (which asks for it), and a sign-in's own unlock where the session is still held back. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: Tizian 「ティツィアーン」 <raisondetredev@pm.me>
This commit is contained in:
parent
f0413531ff
commit
d7855162c7
1 changed files with 548 additions and 95 deletions
|
|
@ -514,6 +514,9 @@ void main() {
|
|||
person: annaOnTodo,
|
||||
authenticator: enrolment.authenticator,
|
||||
code: codeOf(enrolment),
|
||||
proof: device.ownerProof(
|
||||
await remote.beginPasswordChange(session, person: annaOnTodo),
|
||||
),
|
||||
);
|
||||
expect(codes, hasLength(recoveryCodeCount));
|
||||
expect(
|
||||
|
|
@ -746,6 +749,12 @@ void main() {
|
|||
person: annaOnTodo,
|
||||
authenticator: enrolment.authenticator,
|
||||
code: codeOf(enrolment),
|
||||
proof: device.ownerProof(
|
||||
await remote.beginPasswordChange(
|
||||
session,
|
||||
person: annaOnTodo,
|
||||
),
|
||||
),
|
||||
);
|
||||
now = now.add(totpPeriod);
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue