• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Plesk password strength algorithm flawed? / needs improvement

burnleyvic

Regular Pleskian
In plesk panel security policy settings a medium strength password is defined as follows;

These passwords are at least 5 characters long. They consist of characters in upper and lower case and special symbols. Such passwords provide reliable protection from attacks that capture passwords.

If the above is true then how can Password123 and even password123 BOTH be be acceptable medium strength passwords? One lacks a special character and the other lacks a capital letter... There is also the issue of dictionary words being used.

Medium strength should require all of the following: at least one upper case, one number and one special character in a 5 character password. Not contain words from the dictionary, perhaps make this last bit selectable in Security policy section and allow admins to specify custom dictionary file?

So far it seems the only option to fix this is to set password strength to Strong which is defined as;

These passwords are at least 8 characters long. Along with upper and lower-case characters, they require multiple occurrences of digits and special symbols. Such passwords provide strong protection from brute-force attacks.

Testing in panel seems to show that the definition for strong is accurate as it requires upper & lower case, numbers, and special characters to achieve strong so this ones ok though again use of word from dictionary should be factored in as Password123! is defined as strong which is certainly debatable.

also Setting password strength to Very Strong is impractical due to the requirement for a 16 digit password. There are better ways to make a very tough password without just adding more characters.

Parallels can you please consider working on this strength meter as the various strength setting definitions need work with regards to password complexity with current function its still far too easy for a customer to select a substandard password. If parallels is indeed taking security seriously they should consider implementing this as a matter of urgency.
 
Yes, I have reproduced this behaviour and submitted bugreport PPP-9296 to developers.
Thank you for detailed description and cooperation!
 
Last edited:
Hi Igor,

All Lin based servers are at 11.5.30 Update #37, we have #38 to apply this week but i don't see any updates relating to this particular issue. Also while on the subject it would be nice to have a function to prevent email clients from re-entering their old password. Have had more than a few cases where clients re-set their password back to one that's been compromised after a few months and guess what happens. Ideally panel could remember last x password they have used, if that's practical to implement.
 
Back
Top