Extra ‘special characters’ in password

Resolved match79
(@match79)

2 months, 2 weeks ago

The ‘special characters’ list in settings is missing lots of common ones. This causes problems when setting passwords which use other ones (especially auto-generated ones).

Would it be possible to set a longer list (or even allow the list to be customised in settings?)

A good example list is the one provided by OWASP: https://owasp.org/www-community/password-special-characters

!"#$%&'()*+,-./:;<=>?@[\]^_`{|}~

Viewing 7 replies - 1 through 7 (of 7 total)

Plugin Author Wp Enhanced
(@wpenhanced)

2 months, 1 week ago

Sorry for the delay, I started to work on this and didn’t reply 😀

I will release an update this coming week with some new features including a new settings page which will include this setting for you. I made it work with OWASP but also a setting to define what you want.

Will message when released

Thread Starter match79
(@match79)

2 months, 1 week ago

Perfect – many thanks!

Plugin Author Wp Enhanced
(@wpenhanced)

2 months ago

Hi @match79

We have released an update 1.3.0 with this for you

Please update and take a look, it has our new setting pages so you might not fully recognise it – https://docs.wpenhanced.com/frontend-reset-password/feature-overview/security-features

Thanks
Pete

Thread Starter match79
(@match79)

2 months ago

That’s great – just installed and tested and can use the extra characters as requested. Many thanks!

Plugin Author Wp Enhanced
(@wpenhanced)

2 months ago

Amazing!

Have a great week!
Thread Starter match79
(@match79)

2 months ago
Hi,

Typical after sending that message I found a small bug – the password reset page from the special link seems to have a bit of broken html showing up after the New/Re-enter password boxes:
```
New Password
?@[\\\]_{|}~^-]).{8,}$" required autocomplete="new-password" aria-label="New Password" /><br><br>Re-enter Password<br>?@&#091;\\\]_{|}~^-]).{8,}$" required autocomplete="new-password" aria-label="Re-enter Password" />
```
Thread Starter match79
(@match79)

2 months ago

Thanks – yes it’s fixed with 1.3.1

Viewing 7 replies - 1 through 7 (of 7 total)

You must be logged in to reply to this topic.