Skip to content

Tania Sánchez

My feedback

1 result found

  1. 543 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We have serious doubts this function can really increase server security:
    1) Plesk has built-in protection against brute-force on login – it will lock the login form. So no one can try multiple attempts
    2) Arbitrary login name adds very little guess-complexity to a proper password. If you have concerns for your login brute-forced – add another 5-7 characters into your password and feel safe.

    As changed login name is still very likely to be some sort of vocabulary word or derived from your other account name – this function would only give a false sense of better security. Your security strength is in complex password, not in a complex login name. If you have one good password, you don’t need to treat login as your “second password” – one good password is enough.

    As for concerns that default password requirement is set in “weak”, that fail2ban module is not…

    Tania Sánchez supported this idea  · 
    An error occurred while saving the comment
    Tania Sánchez commented  · 

    I'm dissappointed of the fact that this feature is not yet implemented.

    I just upgraded from web admin edition to web pro edition and re-assigned some of the domains (now subscriptions) to a client who used to have access via admin account. Now I need to keep the "admin" username for this client while changing the admin account name and password so it's not longer accesible by them.

    I hope to see this feature in the near future.

Feedback and Knowledge Base