Skip to content

Remembra v5.0.2 — Authorization and Tenant-Isolation Hardening

Choose a tag to compare

@lacrous lacrous released this 24 Sep 17:07
· 146 commits to main since this release

Remembra 5.0.2

V5.0.2 hardens V5 authorization consistency and tenant isolation while preserving V4.9/V5 compatibility. It does not introduce V6 policy, schema, provider, API, or migration implementation.

Security and correctness

  • Adds a centralized, pure authorization evaluator with explicit operation/capability mappings and non-informative denials.
  • Enforces conjunctive organization/project/user/agent visibility across file and SQLite point reads, candidate SQL/counts, search/context, history, audit, entities, batches, snapshots, and scoped migration.
  • Prevents administrative capabilities from erasing explicit project/user/agent selectors; organization-wide access is explicit.
  • Requires tenant:export for full and selected exports and rechecks configured tenant membership before ordinary service work, provider calls, and mutations.
  • Normalizes reserved identity ingress across HTTP/MCP/SDK surfaces and sanitizes provider/IO errors at public boundaries.
  • Applies configured sensitive-data redaction to store, update, and import paths.
  • Preserves the V5.0.1 fail-closed storage, history containment, signed snapshot, and idempotent migration guarantees.

Documentation

  • Finalizes the V5 threat model with assets, trust boundaries, attackers, attack surfaces, controls, residual risks, operator responsibilities, and permanent regression evidence.
  • Documents the exact file-backend, SQLite, snapshot, backup, and transport encryption boundaries; strict mode refuses legacy global Markdown/encryption commands.
  • Adds the V5.0.2 authorization contract and clarifies preflight-versus-atomic snapshot restore behavior.

Verification

  • Node 18.20.8: complete release gate passed.
  • Node 24.21.0: complete release gate passed.
  • Full suite: 431 passed, 0 failed; security matrix: 64 passed; recovery matrix: 13 passed.
  • Documentation check: 36 files passed; dependency audit: 0 vulnerabilities.
  • Package dry-run: 207 files, 422.7 kB compressed; 10K/100K tenant and bounded scale benchmarks passed.

Upgrade and rollback guidance

Read the V5.0.2 authorization contract, V5 threat model, and security/self-hosting guidance before enabling strict tenant operation. Keep a verified backup before applying migrations; failed per-record restore operations are idempotent but may require backup restoration or a verified retry.

Artifacts