Mzack9999
Mzack9999
I think it's way more functional than blind DAST fuzzing as, for example, it allows specific authorization checks like https://github.com/PortSwigger/autorize, that are the most difficult to catch and generally the...
naabu verifies if there is a route to the destination from the `source-ip`, otherwise it fallback to system routes, otherwise it would be impossible to receive the packets from the...
cross-posting linux repro steps: ```console $ docker run -it --cap-add=NET_ADMIN ubuntu:23.10 bash # apt update # apt install apt install golang build-essential git wget curl zip unzip net-tools iproute2 tcpdump...
@JaveleyQAQ It seems like dnsx behaves as expected, as it returns all A records depending on the resolver providing the response. I guess what you are looking for is performing...
@Nyx2022 Thanks for opening this issue. Could you provide more insight about the use case of this feature? I suppose the proxy is potentially blocking clients based on ja3?
@calab33p I've added some more details to the task and added it to our next sprint. Feel free to add more details if you think any functionality is missing or...
Actually resolution happens through UDP|TCP|DOH custom resolvers or system configured one, after that the data socket connection can happen through the socks5 proxy. I've modified the issue you created at...
We have an error like this one: ```console [DBG] Failed 'https://89.28.157.20/index.action': context deadline exceeded (Client.Timeout or context cancellation while reading body) ``` @ehsandeep Shall we consider errors on body read...
@Ice3man543 The body is not available. Attempting to read from the request.Body reader causes the context error. The standard `net/http` doesn't enforce global errors, leaving it up to the user...
`tlsx` requires more investigation as `ClientHello` randomization might conflict with a lot of custom tls settings provided via CLI. Ideally we should only randomize the parts not set via CLI...