This is a trick to detect a crash while fuzzing when doing tests. The fuzzer exits the process with an error code rather than panicking. This test wil

This is a trick to detect a fuzzing output when doing tests. We start the fuzzer in a new process because Frida does not support multi-threaded Starti

Insert a key, value pair that will be converted into the correct json type.

Helper function to create a Tauri `InvokeRequest`. # Arguments `tauri_module` the module the invoked command is part of. Use `None` for a custom Tau

Block calls to `wait`, `waitid` and `waitpid` when they get an error status -1 should be returned in case of failure

Invoke a command but does not try to get the command return value

Check if 'command' calls one of the blocked binaries NOTE: The check only checks if the command contains one of the blocked binary This is a bit loose

The main fn, usually parsing parameters, and starting the fuzzer

NOTE: This is not working on Windows. Binaries are stripped of their symbols and Frida can't find functions of the std lib This is acceptable since we

Check that libc and the instrumented tauri app are in the instrumented module binary

Get the path to `assets/foo.txt`

Invoke a command and get the Tauri command return value

Block access to file with name [`filename`].

Setup a Tauri application context which can call commands from a Tauri plugin. This involves passing the plugin permission and defining the applicatio

Checks if the filename contained in the first register is part of the blocked files

wait status was stored in `storage` Get child process exit status from `storage` and check if it's an error

Policy that blocks creation of child process that executes specified binaries Only blocks child processes that were created through Rust API `std::Com

Block calls to external binaries with the Rust api command function when they return an error

Helper code to create an `InvokeRequest` to send to the Tauri app backend

Helper code to create an `InvokeRequest` to send to the Tauri app backend

Helper code to create an `InvokeRequest` to send to the Tauri app backend

We store the status pointer that was given as argument. This will be used to get the child process exit status

Minimal builder for a Tauri application using the `MockRuntime` NOTE: if your Tauri command uses a state this won't work since it does manage any stat

The default string representation for `Level` is all uppercaps which doesn't mix well with the other printed actions.

Setup a `MockRuntime` with handlers to all the Tauri commands of `mini-app` and access to the plugin `fs:read-files`

Setup the Tauri application mockruntime and an associated "main" webview

Setup the Tauri application mockruntime and an associated "main" webview

Setup the Tauri application mockruntime and an associated "main" webview

Check the function policy in the specified context and if the invocation should be blocked # Panics This may panic if the `Rule` was not built correc

This maps the occurrence of `--verbose` flags to the correct log level

Tauri commands should be allowed at exit when exiting with success status

Control sample where our Tauri commands should not be blocked with no_policy

Tauri commands should be blocked at exit when exiting with error status

Tauri commands should be blocked at entry

Tauri commands should be blocked at exit when exiting from the Rust API with error status

Check if the flag is READ_ONLY

Checks if the flag is READ_ONLY NOTE: flag values seems to differ from the documentation: https://learn.microsoft.com/en-us/windows/win32/api/winternl

Check if the flag is WRITE_ONLY

Checks if the flag is WRITE_ONLY NOTE: flag values seems to differ from the documentation. Refer to the diary for more details

Crash automatically