maneuler / vaultPassword policies and local health
Proposal, not an available feature. No network permission or new data collection is enabled. These RFCs are locally prepared; remote review/merge awaits the owner repository.
Current architecture
The current generator offers a cryptographically random 24-character default, but no policy controls or health dashboard.
Design under review
Add length and class controls using rejection sampling and uniformly shuffle required-class characters. Reject impossible policies. Ship a reviewed, licensed word list for memorable multiword passphrases rather than inventing an unmeasured pronounceable entropy claim. Compute reused/weak/age indicators transiently after unlock; age alone is informational, not a forced rotation rule. Breach status remains unknown until a separately consented check.
Milestones
- M1: entropy/policy specification and deterministic RNG-edge/property tests
- M2: generator controls and documented site-policy presets with no external lookup
- M3: local health view that clears on lock and explains uncertainty
Required acceptance tests
- Requested classes and lengths hold across policy combinations
- Biased modulo sampling and all-disabled policies are rejected
- Health results never appear in persistent unencrypted storage
Limits
Current random generation remains available until the policy generator passes review. A numeric strength score is not a security guarantee.
Any implementation must preserve local unlock/export, add KDBX/KeePassXC regressions for crypto/format changes and update privacy disclosures before new data flows begin.