Repository navigation
Release v19.147.0
Summary
Encryption keys are now guarded by an atomic, monotonic fence on every supported key store, so releasing protected values can no longer race with a fresh erasure.
Added
- Atomic key-store fences for MongoDB, SQL, Azure Key Vault and in-memory key stores, with request-scoped erasure confirmation across stores (part of #4979)
- Bounded protected-value release leases that fail closed on timeout or cancellation (part of #4979)
Changed
- Key stores without fencing support, such as Vault, log a startup warning only; their erasure stays pending until every member advertises the full guarantee (part of #4979)
- Encryption key erasure now requires a MongoDB replica set with majority read and write concerns; a standalone MongoDB cannot provide the linearizable fence and erasure stays pending (part of #4979)
- Encryption key compare-and-swap retries use bounded random jitter (part of #4979)
Fixed
- Protected-value releases are fenced against fresh erasure, and read-model releases hold their lease across paginated reads (part of #4979)