mirror of
https://github.com/fosrl/pangolin.git
synced 2026-05-08 05:39:49 -05:00
[GH-ISSUE #1853] The initial password UI check doesn't work correctly #8792
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/pangolin#8792
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ghost on GitHub (Nov 12, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/1853
Originally assigned to: @miloschwartz on GitHub.
Describe the Bug
When new admin account should be created, there is password check for all the necessities.
I'm using KeePassXC and have this allowed:
Yet I'm getting this check result:
Did check the string and it does have all characters necessary as well.
Yet the special char must be switched off - and after this I'm adding manually one special and one number to pretty long password.
This happened to me for each installation so far.
Environment
To Reproduce
Just standard installation.
Expected Behavior
Should let me pass.
@Pallavikumarimdb commented on GitHub (Nov 13, 2025):
The issue happens because KeePassXC includes some extended ASCII or Unicode symbols (like
¢,§, or½) that pangolin password validator doesn’t currently recognize as valid special characters. The regex only allows a limited ASCII set: [~!`@#$%^&*()_-+={}[]|\:;"'<>,./?]@oschwartz10612 , The current password validator rejects strong passwords containing extended ASCII or Unicode symbols (like § or µ). Should we update the regex to a Unicode-aware version to support all valid special characters while keeping the same strength rules?
@miloschwartz commented on GitHub (Dec 3, 2025):
Closing as not planned because we only plan to support standard ASCII symbols and not all unicode symbols