Matthias
My feedback
10 results found
-
510 votesMatthias
supported this idea
·
-
556 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…
Matthias
supported this idea
·
-
582 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.
—
IGAn error occurred while saving the comment Matthias
supported this idea
·
-
685 votesMatthias
supported this idea
·
-
355 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.
— AY
An error occurred while saving the comment Matthias
commented
Dear Pleskians,
Did you have a look at your licensing models and prices lately?
I mean how ignorant and how arrogant are you, to believe you just have to consider a feature if an enormous number of users think it is important? By the way how many voters do you need at all?Did you ever consider that Plesk is mostly used by Webhosting companies which are eager to offer the most comfortable services to their customers? And did you ever consider that to do so, the Webhosting companies decided that Plesk is THE thing (when pricing was moderate) and switched to Plesk whilst now paying triple as much for your increasingly unstable and more and more buggy solution?
There was a time when Plesk was THE game changer. And now? One mistake chases the next - think of the last incident when Apache Update surprised you because you mod_proxy did not work anymore?Well, Plesk is still a game changer, but not for the best. Your new tactic is to offer a basic framework and remove all sensible features and offer them as an upsell or simply decide we don't need them.
Why are you so curious to see how long it will take till the next unicorn appears and your time is over?
Implement standards like Let's Encrypt for FTP or http/3 for gods sake!
Matthias
supported this idea
·
-
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
Matthias
supported this idea
·
-
295 votes
Please note, Plesk has supported the version of Mailman provided by OS vendor by default.
The Mailman 3 is shipped by default on Ubuntu 18 and Debian 10.
Please keep voting if this request is still actual for you.
—
AAMatthias
supported this idea
·
-
340 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.— SU
Matthias
supported this idea
·
-
303 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.— rk
Matthias
supported this idea
·
-
1,218 votesMatthias
supported this idea
·
You consider to implement HTTP/3 "if it will be popular"??
I mean what do you guys think? HTTP/3 will not prevail or something?