Skip to content

v1.17.2 — Vault write guard and reliability fixes

Choose a tag to compare

View all tags
@RonanDavalan RonanDavalan released this 03 Jul 00:43
v1.17.2
1d8080c

Four fixes addressing a security gap and three reliability issues.

Security

  • The operations journal and mutative-run proof archiving now verify the vault is actually mounted before writing. Previously, if the vault was closed at write time, entries were silently written in clear text to the raw host directory. Both write paths now redirect to the existing local fallback instead.

Reliability

  • Set-of-Mark: repeated captures within the same page no longer leave stale element markers behind, preventing a rare identity collision that could resolve --som-rafraichir to the wrong element.
  • WAF detection: generic vendor names (Cloudflare, Akamai) are now matched only against the page title instead of the full page HTML, eliminating false positives on pages that simply load an ordinary CDN resource. A new --ignorer-waf flag lets the operator override a residual false positive without disabling the signal entirely.
  • --checkpoint: a run stopped by a citizenship cap (max_actions_par_run/max_pages_par_run) no longer loses its progress — it is now treated the same way as a partial failure instead of a completed run.
Assets 2
Loading