• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • 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!
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Issue Strong password security policy isn't accepting strong password

Beau Dilon

New Pleskian
According to the security policy page, a "Strong" password:
These passwords are at least 8 characters long and have at least one occurrence of upper and lower-case characters, digits, and special characters.

However, when trying to create an email account from the CLI, passwords which meet these requirements are being rejected. It seems it needs at least 2 special characters, specifically not just any special character, but one of !,@,#,$,%,^,&,*,?,_,~

This specific requirement should be noted. Here are some example passwords that have been rejected according to the policy:

ahwei.gh6Aih
aeH6doaGeth$
w!9>W9i,6
1]H__O_rW
uNj~4`IZ
 
Last edited:
I wouldn't really call it horribly broken but rather very smart. The only issue it has is that it is not documented correctly. But the approach to dynamically adjust the minimum number of characters based on the variety of the string is some smart piece of software, not just an ordinary algorithm.
 
I wouldn't really call it horribly broken but rather very smart. The only issue it has is that it is not documented correctly. But the approach to dynamically adjust the minimum number of characters based on the variety of the string is some smart piece of software, not just an ordinary algorithm.
I would call accepting 123$%&A (only 7 characters!) as "strong" horribly broken.
 
Agree. A password of 7 characters is from the day before yesterday. I was just wondering why symbols like ~ or > are rejected? There must be a justification behind this, but I cannot figure out any.
 
Back
Top