tauri-capability-hardening

To enforce least privilege for Tauri 2 command exposure, audit exposed commands and map them to minimal necessary capabilities. This restricts frontend interactions with the backend and operating system to specific allowlisted scopes, preventing broad access.

Capability hardening in Tauri is the process of strictly controlling permissions and shell access using explicit capability identifiers. You need it when adding or updating Tauri commands, capability configurations, or remote API routes to minimize security vulnerability impacts.

Restrict shell permissions in a Tauri app by applying allowlisted command scopes and enforcing strict capability merging. This prevents broad shell access and mitigates risks from untrusted frontend input interacting with the operating system.

Auditing remote API routes in Tauri 2 requires reviewing all exposed routes and applying least-privilege boundaries. This ensures frontend code can only interact with explicitly mapped backend commands and not general operating system resources.

Yes, the capability hardening process supports read-only file system access by granting Tauri commands specific directory permissions. This ensures commands receive only minimal necessary capabilities instead of broad general write permissions.