Login with individual loginname instead of login=emailadress
Needs Review
To prevent bruteforce login success an option to change loginnames from the emailadress to an individual loginname would be nice.
This is not something we will consider. The various accounts that follow the format of user@example.com require that format in order to be unique on the server. If we allowed login within the domain portion then a given email address (for example) could only be used once on the server.
cPanel & WHM are most commonly used on servers with 10s, 100s, or 1000s of accounts, with corresponding domains. If we suddenly began restricting email addresses on those systems it would cause significant support costs and drive people away from their service providers, and cPanel & WHM.
This is not something we will consider. The various accounts that follow the format of user@example.com require that format in order to be unique on the server. If we allowed login within the domain portion then a given email address (for example) could only be used once on the server.
cPanel & WHM are most commonly used on servers with 10s, 100s, or 1000s of accounts, with corresponding domains. If we suddenly began restricting email addresses on those systems it would cause significant support costs and drive people away from their service providers, and cPanel & WHM.
Your reasoning sounds like nobody could offer a solution. There are many shades of grey between black and white.
Userprefix on mysql databases where following the same reasoning.
Five years ago there weren't many cpanel specific attacks. Now I see them every day on ports and with the knowledge of username=emailaddress. And complex passwords drive away customers too.
Perhaps a prefix or suffix generated when creation the account or domain can be added to the emailadress to form the username. That way a check for collision could be reduced to the time when creation a new account.
Your reasoning sounds like nobody could offer a solution. There are many shades of grey between black and white.
Userprefix on mysql databases where following the same reasoning.
Five years ago there weren't many cpanel specific attacks. Now I see them every day on ports and with the knowledge of username=emailaddress. And complex passwords drive away customers too.
Perhaps a prefix or suffix generated when creation the account or domain can be added to the emailadress to form the username. That way a check for collision could be reduced to the time when creation a new account.
Replies have been locked on this page!