Repository navigation
Rampart 1.9.0
Rampart 1.9.0
Rampart 1.9.0 adds optional production controls, bounded service diagnostics and experimental external audit witnessing, alongside a website and documentation refresh.
Added
- Opt-in production guard — Require approval for the documented infrastructure
and migration CLI mutations and explicitly named production Kubernetes targets.
Keep the base policy installed; implicit Kubernetes targets and native typed
MCP tools are outside this profile's scope. - Bounded service diagnostics — Managed background and launchd logging rotates
at 10 MiB with three backups, preserving owner permissions and redacting managed
records.serve --log-fileexposes the same writer for custom setups. Existing
launchd installations adopt it after reinstalling their owned service definition. - Experimental external audit witness — Publish small checkpoints to separately
administered file storage or an operator-provided authenticated HTTPS endpoint,
and verify retained checkpoints against local history. This optional client
does not provision a service or establish independent storage administration.
Changed
- A coordinated website and documentation refresh — A short architectural
scroll illustration connects actions, policy and audit records, followed by
the install, protect and verify journey. Static mobile, reduced-motion and
no-JavaScript fallbacks preserve useful content. MkDocs retains its existing
architecture and URLs with improved navigation, typography and themes. - Clearer troubleshooting and feedback — Current setup and verification
commands replace stale service and repair instructions. A structured bug form
gathers minimal redacted reports and keeps security disclosures private. - More meaningful regression checks — Isolate setup fixtures, require actual
MCP and audit output, restore engine fuzz inputs previously skipped by a stale
fixture, and exercise the real HTTP handler. Consolidate duplicate preset
checks, verify effective Windows handle permissions, and build docs strictly.
Fixed
- Hermes v0.21.1 native approvals — Recognize the host's additional approval
dispatcher while preserving approval identity checks and older supported
resolver paths. Keep working-directory identity correct across supported
Hermes paths. Unrecognized approval flows continue to block safely.
Upgrading and scope
Follow the upgrade guide to refresh the binary and Rampart-managed integration entries while preserving user-owned configuration, policies and audit state. Keep the approval journal, its identity key and its one-time approval state together when backing up or restoring.
Existing launchd users must reinstall their managed service definition to adopt bounded diagnostics, retaining any non-default service flags. Linux services continue to use journald; diagnostic-log rotation is separate from audit retention.
The production guard is opt-in. External witnessing remains experimental and requires independently administered storage; unwitnessed events remain outside its guarantee. Hermes remains experimental, with bundled adapter version 1.7.2. Integration-specific support limits remain documented in the support matrix.