Huskynarr
My feedback
-
433 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.
—
IGHuskynarr
supported this idea
·
-
8 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.
—
IGHuskynarr
supported this idea
·
-
9 votesHuskynarr
supported this idea
·
-
14 votesHuskynarr
supported this idea
·
-
167 votes
Thank you for your input. We will explore the possibility of implementing YubiKey in upcoming releases.
Huskynarr
supported this idea
·
-
28 votesopen discussion · 4 comments · Feature Suggestions » Extensions · Flag idea as inappropriate… · Admin →Huskynarr
supported this idea
·
-
45 votes
Could you explain why total subscription size is not enough? Why you would need a separate limit for mail content and web content?
UPD: reopened after new comments received
An error occurred while saving the comment Huskynarr
supported this idea
·
-
121 votesopen discussion · 29 comments · Feature Suggestions » Usability and UI · Flag idea as inappropriate… · Admin →Huskynarr
supported this idea
·
An error occurred while saving the comment Huskynarr
commented
Add an Notice Block to add Seperate Informations on the IP's.
-
17 votesopen discussion · 2 comments · Feature Suggestions » Web / HTTP functions · Flag idea as inappropriate… · Admin →Huskynarr
shared this idea
·
-
644 votesHuskynarr
supported this idea
·
-
497 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…
Huskynarr
supported this idea
·
-
1,498 votes
We hear you and see a clear demand for this feature.
I want to say that implementing these features requires a lot of investment, and in 2021 Plesk team keeps focusing on the delivery of other improvements (sad, but true).
We will back to the re-evaluation of these features at the beginning of the next year.
Please continue to share your use cases and requirements, and it would really helpful if you point to existing solutions that we can review and check before implementation.
Your feedback is important to us. Thank you, everyone.
—
AAHuskynarr
supported this idea
·
-
98 votes
We are building an extension to help you use Composer straight from the Plesk interface. Help us make a better solution for you by taking a survey on how you use Composer.
The survey will take 4-6 minutes:
https://pt-research.typeform.com/to/LyPiPGBeta version of the Extension is available for Plesk Obsidian: https://docs.plesk.com/release-notes/obsidian/whats-new/
Huskynarr
supported this idea
·
-
403 votes
Thank you for your input. We will definitely look into integrating DynDNS in our future releases
Huskynarr
supported this idea
·
That would be really important.