H0r53

Example Chrome headers when sent to my own local HTTP server for traffic inspection. ```http Host: 0.0.0.0:5000 Connection: keep-alive Upgrade-Insecure-Requests: 1 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36...

I'm using Chrome in either case and my understanding is TLS fingerprinting should not be an issue if the agent is Chrome. That could be what is detecting HTTP Toolkit,...

@pimterry thanks for your detailed and informative response. I performed the following test to rule out TLS fingerprinting on the particular website I've experienced issues with. - Navigate to target...

Fortunately, I was able to find a few workarounds. I'm able to capture and decrypt the traffic in WireShark. If you're using Chrome for example, you can set a SSLKEYLOG...

Thank you for the update! I'm not exactly sure what version I was using before but after launching HTTP Toolkit is now reporting `Version 1.7.0 (1.7.0)`. I opened a new...

Same issue with a freshly cloned repo. Did you ever find a solution?

It feels hacky but I tried the following: ``` var threads = Process.enumerateThreadsSync() var currentThreadId = Process.getCurrentThreadId() for (var thread of threads) { if (thread.id === currentThreadId) { console.log("FOUND") }...

I'm still not sure why the current Thread ID isn't included in `Process.enumerateThreads()`, but I did find a way to access the Thread context from frida Stalker. The idea is...

I've encountered an issue where the `iterator.putCallout(onMatch)` method does not work well. In particular, when attempting to use `send`/`recv` within Frida Stalker. It seems that `putCallout` puts some callback on...

A follow up to this is, **can you setup frida to essentially "break" on a particular address and then do something like dump the current context**? My guess is frida...