You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 30, 2024. It is now read-only.
In addition to #357, Flask-Security gives attackers hints to whether the username or password is invalid. Even if you change SECURITY_MSG_USER_DOES_NOT_EXIST and SECURITY_MSG_INVALID_PASSWORD to use ambiguous wording, talking to the login view via JSON (for example) will still give hints whether the email or password is incorrect.
For an invalid password, the response looks like:
{'meta': {'code': 400},
'response': {'errors': {'password': ['Invalid username or password']}}}
And a non existent user:
{'meta': {'code': 400},
'response': {'errors': {'email': ['Invalid username or password']}}}
The text was updated successfully, but these errors were encountered:
* Fix backwards compat issues with permissions.
Now - if an app uses fsqla_vX it just works.
Added description in CHANGES on how apps that don't use fsqla_vX need to be modified.
Added some tests to verify working with older DBs.
The fsqlalchemy example was crazy - trying to use mocks made everything very complex. Converted to a simpler in-memory DB style testing.
closespallets-eco#673
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In addition to #357, Flask-Security gives attackers hints to whether the username or password is invalid. Even if you change
SECURITY_MSG_USER_DOES_NOT_EXIST
andSECURITY_MSG_INVALID_PASSWORD
to use ambiguous wording, talking to the login view via JSON (for example) will still give hints whether the email or password is incorrect.For an invalid password, the response looks like:
And a non existent user:
The text was updated successfully, but these errors were encountered: