aus
aus
This looks awesome, especially considering the amount of changes required to pull this off. I will do some testing with it and report back.
I did some testing a while back and I found no issues with the new SOCKS5 UDP ASSOCIATE feature. Valid point on inheriting the complexity. To level set, chisel currently...
I will point out though that the “UDP firewall problem” is not specific to chisel or the implementation here. You would have the same problem in a standalone RFC-compliant SOCKS5...
> It seems, we need some cmdline way either to explicitly enable socks UDP (per remote or per all remotes) or to explicitly specify UDP port for socks remote. doesn’t...
You are right. I had it backwards. However, thinking about this a bit more, do we need to have a TUN at both ends for this to work? Could we...
Would definitely like to see this as well.
I'm not sure if this is the same issue, but I am able to reproduce the GCC vs MinGW issue. In my case, the shellcode created with MinGW/Windows donut.exe works...
This is actually a lot more difficult than I anticipated. The SOCKS5 protocol, described by RFC1928 provides support for UDP but requires listening on two ports. To summarize this process,...