new·The score now tells you which way it movedA brain's exam only ever grows: its own material writes questions, and so does every question a real caller asked and did not get answered. The score is a percentage over that growing set, so a brain that learned more could post a smaller number — and this week three did. One of them answered two MORE questions than the week before and showed eighteen points less. Printed as a single percentage, that reads as decline to a reader and as punishment to anyone who contributes material.all news →
mozg.beta
Sign in

Tauri · all subjects

security & permissions

5 notes, read out of this brain and free to use. Each one was extracted from a source and is re-checked against its exam.

Isolation application best practices

Because the Isolation application protects against Development Threats, it should be kept as simple as possible. Dependencies of the Isolation application should be minimal, and required build steps should be minimal to avoid needing to worry about supply chain attacks against the Isolation application on top of frontend application threats.

Isolation Pattern purpose and use

The Isolation Pattern is a method to intercept and modify Tauri API messages using JavaScript before they reach the Tauri core, protecting applications from unwanted or malicious frontend calls. Tauri strongly recommends always using the Isolation Pattern when possible, as it intercepts all messages from the frontend.

Isolation Pattern threat model

The Isolation Pattern was designed to address build-time threats that arise from untrusted content executed in the frontend. Many frontend build tools and complex applications consist of deeply nested dependencies, often dozens or hundreds, which are bundled into the final output, creating supply chain attack vectors.

Isolation Pattern IPC validation recommendation

Tauri strongly recommends locking down applications by validating IPC input using the Isolation Pattern. Developers should ensure that input is within expected parameter ranges, such as verifying file read/write calls do not access unexpected paths, or that HTTP fetch calls only set Origin headers that the application expects.

Isolation Pattern application design recommendation

Isolation Pattern applications should be kept as simple as possible since their purpose is to protect against build-time threats. Minimize dependencies and necessary build steps to avoid supply chain attacks on the Isolation Pattern application that wraps the frontend application.

Give your agent this brain