Repository navigation
v2.5.7
HexDB 2.5.7 fixes what an independent re-review of 2.5.6 found: a write that could move a document out of a row-restricted role's protection, a dead letter that could be stored but not delivered, plugins skipping changes after a new Overseer, and four smaller issues. Upgrade every hex.
Security
- Moving a row can't reveal its protected fields. A user holding a row-restricted role that hides a field (tenant A,
secrethidden) and another role for other rows (tenant B) could change onlytenantfrom A to B and then readsecret. A write that would leave a value showing more than it did (hidden before and not after, or masked before and less masked after) is now refused, for patch, replace, transactions and update by filter.
Delivery
- Dead letters always arrive. A receive on the dead-letter queue that ran just as a message was being moved there could make the message invisible until the queue's index was rebuilt. It's now looked for again until its move commits.
- Plugins after a new Overseer. A stream plugin continued from the end of a new Overseer's history, skipping changes it hadn't received. It now continues from where the new Overseer's history holds the old one (a few changes may come again: deduplicate on
seq). - Plugin SDK retries.
api()sends a write again after an uncertain answer only where the server applies it once perIdempotency-Key(document writes, transactions), never a queue send or stream publish.
Fixed
- Script children. Processes a script starts in the background now stop when it finishes, not only when it times out.
- SQL memory. SQL reads documents 32 at a time and stops as soon as
limits.sql_max_mbis passed, instead of checking after the whole read. - API keys after a lattice-secret rotation. A key used only on replicas kept failing after the old secret was removed; replicas now ask the Overseer again until it confirms the key's new hash.
Upgrading
Restart the hexes one at a time, as usual: replicas first, the Overseer last.
Full Changelog: v2.5.6...v2.5.7