isolation pattern and a capability file that says why for every permission #11

New Issue

grenade · 2026-09-15T12:37:16Z

grenade commented

2026-09-15 12:37:16 +00:00

Parent: #1

Scope

Turn on Tauri's isolation pattern (app.security.pattern = isolation with an isolation/ entry that the CLI bundles), keep the CSP with no remote sources, and make capabilities/default.json the only capability, granting core:default and nothing else. Add a small test (a script in CI is fine) that fails if any capability entry lacks a description.

Acceptance

cargo tauri dev runs with isolation active (the IPC payloads are encrypted in the devtools network tab). A capability file with an undescribed permission fails CI.

Depends on

Nothing; first child of the epic.

Parent: #1 ## Scope Turn on Tauri's isolation pattern (`app.security.pattern = isolation` with an `isolation/` entry that the CLI bundles), keep the CSP with no remote sources, and make `capabilities/default.json` the only capability, granting `core:default` and nothing else. Add a small test (a script in CI is fine) that fails if any capability entry lacks a `description`. ## Acceptance `cargo tauri dev` runs with isolation active (the IPC payloads are encrypted in the devtools network tab). A capability file with an undescribed permission fails CI. ## Depends on Nothing; first child of the epic.

grenade added the child label 2026-09-15 12:38:51 +00:00

grenade referenced this issue

2026-09-15 12:41:11 +00:00

a threat model in the repo that matches the code #48

grenade referenced this issue

2026-09-15 12:42:32 +00:00

epic: workspace, toolchain and CI gate #1

grenade referenced this issue

2026-09-15 12:42:48 +00:00

epic: security hardening and release readiness #10

grenade referenced this issue from a commit

2026-09-15 15:07:53 +00:00