Files
reverse-engineering-anything/docs/guides/runtime
morluto 9699ce9057 fix(frida)!: require an absolute script path over MCP (#11580)
* fix(frida)!: require an absolute script path over MCP

`load_frida_script` and `instrument_with_frida` admitted a relative script
`path`, which the MCP server read against its own working directory rather
than the caller's. Both contracts now admit only an absolute local path, as
the pcap and debugger contracts do. The `instrument-with-frida` CLI resolves a
relative `--script-file` against its working directory before the contract
sees it. `program` is unchanged: on a remote device it may name a path there.

BREAKING CHANGE: MCP `load_frida_script` and `instrument_with_frida` refuse a
relative script `path` with `invalid_request`; send an absolute path. CLI
`--script-file` still accepts a relative path, and Evidence `source_path` is
now the resolved absolute path.

Fixes #11506

* test(frida): assert a refused relative script path starts and loads nothing

* test(frida): verify the CLI fixture's script file spelling is relative

* test(frida): give the contract test an absolute script file

The load and instrument contracts admit only an absolute script path, so
the contract test's relative script.js no longer parsed. Use a resolved
path for the accepted inputs and refuse the relative spelling in its own
test.

* test(frida): drop the contract-level relative path check the MCP test covers
2026-11-16 08:54:51 +08:00
..