Daemon: key cache, idle eviction and secret lifetimes
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 15/100
Research direction
The issue names no source files, tests or entry points, so the first step is to read the referenced issues #147-#150, #100, #103 and #212 and the existing SecretBytes type. The checklist asks for a written current-state analysis and approval before any code change, so the first deliverable is that plan. Done means an approved plan covering cache limits, idle eviction, zeroization and mlock behaviour, with a small follow-up PR.
Written by the indexing model from the issue text.
Description
Ziel und Abgrenzung
Native Daemon-Lebensdauer von Secrets: Cache-Limits, Idle-Timeouts, Entsperrfenster, Zeroization bei Evict/Shutdown/Cancel, Nebenläufigkeit, Crash-Grenzen und mlock/VirtualLock prüfen. Vorhandene SecretBytes wiederverwenden, keine zweite Speicherverwaltung oder XOR-Masking. #212 nutzt später diese native Funktion statt eigener Cache-Logik.
Priorität und Abhängigkeiten
- P1
- #147–#150, #100, #103; Schnittstelle #212
Verbindliche Umsetzung
- Ist-Zustand, betroffene Dateien, Sicherheitsrisiken und Plan vor Änderungen dokumentieren; Freigabe einholen.
- Ein kleiner unabhängiger PR; keine ungeplanten Refactorings, keine ungesicherte Netzwerkfreigabe.
- Positiv-, Negativ-, Manipulations-, Abbruch-, Grenzwert- und Regressionstests nach Scope.
- CI Windows/Linux soweit relevant, fmt/clippy/tests/Security-Checks grün.
- Bestehende Schlüssel, CLI/API, Pakete und .pqkf v1/v2 bleiben kompatibel.
- Dokumentation Deutsch/Englisch, Review, Definition of Done und Rollback nachgewiesen.
Rollback
ADR/PR revertieren oder opt-in Feature deaktivieren. Keine automatische Datenmigration; bestehende Installationen bleiben unverändert.
- Dominant language
- Rust
- Stars
- 0
- Forks
- 0
- Avg merge
- 1h 22m
- Merged PRs (30d)
- 72
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from SpecterAoD/pqkeep
-
area:cli good first issue help wanted needs translation priority:P2 type:documentation
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
SpecterAoD/pqkeep#226 ·
Maintainers usually reply within 1 day
-
area:community good first issue help wanted priority:P2 type:documentation
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
SpecterAoD/pqkeep#225 ·
Maintainers usually reply within 1 day
-
area:cli good first issue priority:P2 type:documentation
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
SpecterAoD/pqkeep#224 ·
Maintainers usually reply within 1 day
-
area:release good first issue priority:P2 type:documentation
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
SpecterAoD/pqkeep#223 ·
Maintainers usually reply within 1 day
-
area:cli good first issue priority:P2 type:maintenance
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
SpecterAoD/pqkeep#222 ·
Maintainers usually reply within 1 day
All issues in SpecterAoD/pqkeep
Similar issues
-
ライブラリを追加Openpriority middle
Difficulty 1/5 Under an hour Newbie friendliness 62/100
KATO-Hiro/AtCoderClans#13015 ·
Maintainers usually reply within 1 day
-
needs-review
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
UCS-Care-Group/mailcraft#1429 ·
Maintainers usually reply within 1 day
-
priority: medium ready
Difficulty 1/5 Under an hour Newbie friendliness 88/100
TusanHomichi/PSIV#646 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
area:tui bug P1
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
agent-of-empires/agent-of-empires#5705 · 1 comment ·
Maintainers usually reply within 1 day