linux-credentials / linux-credentials/oo7
Local keyring backups
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 373
- Forks
- 39
- Avg merge
- 14h 2m
- Merged PRs (30d)
- 14
Description
When the keyring gets corrupted that can have really bad consequences, as we've seen during the recent migration. It'd be good to minimize the chances of completely losing the keyring. Since it's not much data, I wonder if we could just make a new copy every time something changes, or something similar? That way even if the active keyring file is corrupted you always have the older keyring files.
Contributor guide
No contributing guide indexed for this repository
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
No file or test is named. Start by locating the keyring persistence and update entry points, then inspect how the recent migration handles corruption. Done means a corrupted active keyring can be replaced or recovered from an older copy without losing the stored data.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100