You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Post-review corrections to the security-hardening branch before merging
to main:
- keyring: sanitize names on load instead of rejecting the file. One
out-of-policy entry in a hand-edited keys.json made the whole registry
unloadable, and callers that fall back to an empty registry on error
(GUI rename) would then save and destroy every other entry.
- publish: crates.io order published keyroost-resolve before its
dependency keyroost-transport, which fails the first tag run; same
ordering corrected in the TODO runbook.
- publish: pin wingetcreate.exe to a versioned release and verify its
SHA-256 before running it with the winget token — matches the SHA
pinning applied to every action in the same file.
- qr: one malformed otpauth payload no longer discards accounts decoded
from the other QR codes in the same image; it becomes a skip, and the
underlying error is surfaced only when nothing in the image parses.
- keyroostctl: `import --qr` now prints the "QR i of n" notice for
multi-code Google Authenticator exports (a clean 1-account import of
QR 1 read as "migration complete"), and the 0-account error no longer
suggests import-file, which would equally find nothing.
- SECURITY.md: scope the zeroize-on-drop claim to what is implemented;
imported seed buffers are tracked in TODO-hardening.md instead.
- udev: correct the ID_SECURITY_TOKEN attribution (fido_id builtin, not
hwdb) and document that the generic rule needs systemd-udevd.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
0 commit comments