My feedback

2 results found

1. Rename database

   211 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   planned  ·  3 comments  ·  Feature Suggestions » Databases  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   An error occurred while saving the comment
   Ryan11433 commented  ·  Jul 19, 2013  ·  Edit…  ·  Delete…

   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.

   Save Submitting...
   Ryan11433 supported this idea  ·  Jul 19, 2013

2. Change admin username

   532 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   68 comments  ·  Feature Suggestions » Security  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   open discussion  ·  AdminSergey L (CTO, Plesk International GmbH) responded

   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 enabled by default or may consume extra resources, etc – they are much irrelevant here. If someone is not willing investing some time into setting better password, into changing password policy or into installing/enabling server protection – changed admin name will again be only a false sense of security. If a password is “1234567”, then login doesn’t really matter.

   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… more

   Ryan11433 supported this idea  ·  Jul 19, 2013
   An error occurred while saving the comment
   Ryan11433 commented  ·  Jul 19, 2013  ·  Edit…  ·  Delete…

   that seem like a good idea

   Save Submitting...