erp5_core: Password Tool should not leak info on users
for security reasons, info on users, or existence of usernames shouldn't be leaked from the system.
-
Owner
@Nicolas BTW, what about CredentialRequest_checkLoginAvailability ? ( and callers such as ERP5Site_newCredentialRequest )
-
Developer
Hi,
IMO the case for Credential Requests is different, as we let customers choose their own login. So at some point we need to inform them that the login they choose is not available. Maybe we could have a generic message instead (ie, "Selected login is not valid", in https://lab.nexedi.com/nexedi/erp5/blob/master/bt5/erp5_credential/SkinTemplateItem/portal_skins/erp5_credential/ERP5Site_newCredentialRequest.py#L14), but attackers wouldn't be duped.
I would argue that this use of Credential Requests is a bad practice, and should be avoided in projects :)
What do you think ?
-
Owner
Thanks, maybe we could just change
CredentialRequest_checkLoginAvailability
to not allow calling it directly. -
Owner
I looked a bit more and found https://cheatsheetseries.owasp.org/cheatsheets/Authentication_Cheat_Sheet.html#account-creation . ( this is in context of !1795 )