Oleks
My feedback
5 results found
-
371 votes
As UserVoice staff cleaned up the most of twisted voices, I’ve returning this suggestion to open discussion.
Everyone, please continue voting for this feature if you consider it important.
—IB
An error occurred while saving the comment -
1,198 votes
An error occurred while saving the comment Oleks commented
Why is this still an open discussion?
There are many reasons to add ClamAV, let's just say that at least not anyone has the money (or will) to spend upwards of $300 per year per plesk install just for mediocre to somewhat okay protection, especially if most (if not all) is covered with ClamAV.Why do I have to manually set up ClamAV every time (yes, it definietly is possible, though tiring)?
Oleks supported this idea ·
-
543 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…
Oleks supported this idea ·
-
23 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
Oleks supported this idea ·
-
1,071 votes
Hi all, Thanks for your input, really appreciate this! As you know, in Plesk Onyx 17.8 we made a significant improvement that allows you to use several cloud storages or even SFTP for remote backups. In Plesk Onyx 17.9 we will continue to improve Plesk Backup Manager in general and Flexible Backup Scheduler Manager in particular.
Based on the initial description and comments I can highlight 3 scenarios in the scope of this request:
#1. Keep Daily & Weekly & Monthly backups at the same time: (Example: 2 weeks of daily backups + weekly backups by each Monday)
#2. Backup to different storages (like daily to FTP and monthly to Google Drive)
#3. Multiple Storages of the same type (like 2 different FTP servers)
ID in our Issue Tracker: PPM-1701
-DLOleks supported this idea ·
Yes, vote!
Maybe then they'll stop ignoring all top feature suggestions for years now.
**** I'm happy I switched from Plesk.