Skip to content

0.1.0a10

Pre-release
Pre-release

Choose a tag to compare

View all tags
@spiderings spiderings released this 31 Jul 10:46
· 68 commits to dev since this release
v0.1.0a10
8777978
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Release 0.1.0a10 — a single follow-up fix to the audit-log encryption indicator shipped in 0.1.0a9 (#80, #81).

No breaking changes. The 0.1.0a9 notes still apply for the ENC:v3 gateway wire and the removal of keyvault enable-se --unattended.

Fixes

  • status reported audit log plaintext (no audit wrapping key) for a legacy keyvault profile whose audit log is in fact MRAL-encrypted (#80). The 0.1.0a9 indicator decided solely on the AUDIT_KEY_FIELD / PENDING_AUDIT_KEY_FIELD manifest records, but those are written only by wizard/_keyvault_init, so a keyvault created before 0.1.0a9's profile-scoped native key ids never carries either. privacy_check/audit.py treats exactly that shape as a supported branch ("Pre-profile-scoping metadata selects the legacy global audit key"), resolves the legacy global key, and encrypts normally — so the new indicator contradicted the on-disk state on every pre-0.1.0a9 install. The verdict now has a legacy branch that reads the audit log's own MRAL header, because the manifest cannot prove either outcome there and claiming encrypted unconditionally would be a false positive (the legacy key has a real history of becoming unusable with a silent plaintext fallback). Committed, pending, and scoped verdicts are unchanged. The risk was operator action rather than data exposure: the line erred pessimistic, but someone trusting it could have run destructive keyvault ceremonies against a healthy encrypted setup.

Changes

  • Version bumped to 0.1.0a10 across all pinned surfaces (#81).
Assets 2
Loading