Skip to content

docs: refresh the encryption roadmap after 2.4.0#25

Merged
jdatcmd merged 1 commit into
mainfrom
docs/roadmap-refresh-2.4.0
Jul 16, 2026
Merged

docs: refresh the encryption roadmap after 2.4.0#25
jdatcmd merged 1 commit into
mainfrom
docs/roadmap-refresh-2.4.0

Conversation

@jdatcmd

@jdatcmd jdatcmd commented Jul 16, 2026

Copy link
Copy Markdown
Contributor

Updates design/encryption-roadmap.md to reflect the 2.3.0 and 2.4.0 releases:

  • What exists today: drops the AES-CBC data ciphers (removed in 2.4.0; XTS only), adds the 2.4.0 key-metadata integrity and the per-file temp-file salt, and notes the confidentiality-only and unlogged-fork limitations.
  • Suggested sequencing: reframed as the near-term (de facto 2.5) plan with shipped items removed (temp files, AES-256-XTS, FIPS, the security review); PG19 port added as a parallel track.
  • Cloud KMS providers: expanded with the secret-store vs envelope integration models and their implication for the key-provider interface (envelope needs a wrap/unwrap op; secret-store fits the current keyring_get_key as-is).

Planning doc only; not part of the published docs site.

🤖 Generated with Claude Code

Bring the roadmap up to date with the 2.3.0 and 2.4.0 releases:

- Drop the removed AES-CBC data ciphers from "what exists today" and note
  data files are XTS only; add the 2.4.0 key-metadata integrity and the
  per-file temporary-file salt; note the documented confidentiality-only
  and unlogged-fork limitations.
- Reframe "Suggested sequencing" as the near-term (de facto 2.5) plan with
  the shipped items removed, and add the PostgreSQL 19 port as a parallel
  track.
- Expand the cloud KMS providers feature with the secret-store vs envelope
  integration models and their effect on the key-provider interface.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@jdatcmd jdatcmd merged commit 15616ca into main Jul 16, 2026
20 of 26 checks passed
@jdatcmd jdatcmd deleted the docs/roadmap-refresh-2.4.0 branch July 16, 2026 14:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants