fix(auth): every call with a code after the password takes the address
Whoever guessed codes decided whether the owner was mailed (the re-review's fourth finding): the address a sign-in sent was optional, so a guesser left it out and no mail went, and a wait begun without a mail used up the one mail there was. Every call carrying a code after the password or the phrase proved (signing in, the phrase's reset, a change of password, a new phrase, deletion) now takes the account's address and the language of its mails, and is refused (wrongCredentials, as anything wrong after the password) before any code is checked when the address isn't the account's; every wait mails the owner, not only the first. The app sends the address the person typed, or for changes while signed in the one this device signed in with, and says so where it doesn't know it (addressUnknown). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: Tizian 「ティツィアーン」 <raisondetredev@pm.me>
This commit is contained in:
parent
e8c4a3d472
commit
2a21672b43
1 changed files with 795 additions and 347 deletions
|
|
@ -186,6 +186,8 @@ void main() {
|
|||
password: 'correct horse',
|
||||
crypto: dependencies.crypto,
|
||||
);
|
||||
// The address this device signed in with, which deleting sends.
|
||||
dependencies.addresses.addresses[person] = 'anna@example.org';
|
||||
Finder field(String label) => find.widgetWithText(TextField, label);
|
||||
|
||||
await tester.tap(find.text('Delete account'));
|
||||
|
|
|
|||
Loading…
Reference in a new issue