Consider Separate Password Input
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 30.6k
- Forks
- 2.1k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 72
Description
I'm wondering if other users would find it useful to have a password input widget which returns a https://docs.rs/zeroize/latest/zeroize string. I'm working on an application which would benefit from this at the moment, though admittedly the security concern is somewhat limited. It does follow from guidance here: https://github.com/veorq/cryptocoding?tab=readme-ov-file#clean-memory-of-secret-data
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the existing password input widget and the linked zeroize and cryptocoding guidance to understand the proposed API and memory-safety requirements. Define what a separate widget returning a zeroize string should guarantee, then document or validate the design with the maintainers before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- frontend, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100