GB
My feedback
25 results found
-
272 votes
Thank you for your input! We will consider this functionality in upcoming releases if it will be popular.
Everyone, please continue voting for this feature if you consider it important.
— IB
GB supported this idea ·
-
291 votes
The previous status was set by mistake.
Due to the changes in MongoDB’s licensing we are no longer able to consider this as a potential feature to be added to our product.
Please continue to vote if you would like to use CouchDB in Plesk.
—
AAGB supported this idea ·
-
430 votes
GB supported this idea ·
-
421 votes
Thank you for your input! We will consider this functionality in upcoming releases if it will be popular.
Everyone, please continue voting for this feature if you consider it important.
—
IGGB supported this idea ·
-
559 votes
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…
GB supported this idea ·