| Summary: | Backend-specific password length limits are not reported or respected during initial vault creation | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | tneo |
| Component: | Vaults widget | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | CONFIRMED --- | ||
| Severity: | normal | CC: | ivan.cukic, nate |
| Priority: | NOR | Keywords: | usability |
| Version First Reported In: | 6.0.0 | ||
| Target Milestone: | 1.0 | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
tneo
2022-03-29 15:46:17 UTC
I tested this a bit more the password length is limited to 32 characters. Longer passwords silently get truncated. This should either be unlimited, or the user should be notified upon creation of the vault what the limit is. Sorry for the spam, but I can't edit my comment above. Limit is 32 characters. Inserting 33 character passphrase creates a Vault. Lock the vault and try to unlock the Vault. The 33 character passphrase is not accepted and reducing this to 32 character does not unlock either. It is not entirely clear what happens here upon passphrase creation. Which backend are you using for the vault? cryfs, encfs or gocryptfs Sorry forgot that part: CryFS |