Ryan11433

My feedback

  1. 157 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    planned  ·  3 comments  ·  Feature Suggestions » Databases  ·  Flag idea as inappropriate…  ·  Admin →
    Ryan11433 commented  · 

    Good idea this have happened to me before few years ago that I had to another way is to create another database with the renamed database transferred from the database that was not renamed. Rename database is a necessary feature.

    Ryan11433 supported this idea  · 
  2. 366 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    44 comments  ·  Feature Suggestions » Security  ·  Flag idea as inappropriate…  ·  Admin →

    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…

    Ryan11433 supported this idea  · 
    Ryan11433 commented  · 

    that seem like a good idea

Feedback and Knowledge Base