Aviram Hassan
Aviram Hassan
Hey Dan, I'm working on a refactor to the e2e, I'll probably do it in Python so writing e2e tests will be a bit easier (less concerns about safety &...
@thedanvail I hope all is well! I'm not planning to implement it, but just saying it might need to have a bit of changes to match the new design.
Done @TawalMc ! Let us know if you need any help :)
> Can you add #[trace] and #[notrace]? https://docs.rs/rstest/latest/rstest/attr.rstest.html#trace-input-arguments ``` 641 | pub async fn test_remote_env_vars_exclude_works(#[future] service: EchoService) { | ^^^^^^^ `impl futures_util::Future` cannot be formatted using `{:?}` because it doesn't...
It's for the client side stuff - cli and dylib. It would make it easier to run the binary without having to authorizing it manually. It shouldn't be a code...
I think this issue should be broken into few parts, here's a suggestion: 1. DNS Resolving - This should be done by hooking `getaddrbyname` and `getaddrinfo`. Should be a flag....
> When would it make sense to turn on ENABLE_TCP without ENABLE_DNS? When the services are accessible from your existing network I guess? but my thought was to split it...
To be more precise, we need to add E2E test to run both on macOS/Linux and for Linux to work we probably need to alter the current Go Linux hooks...
Just found about https://github.com/frida/frida-gum/issues/439 suggesting to pass dummy variables to fill up the registers, this could work.
Found a workaround, leaving this open until upstream is fixed