mhddos_proxy icon indicating copy to clipboard operation
mhddos_proxy copied to clipboard

DEPRECATED - https://github.com/porthole-ascend-cinnamon/mhddos_proxy_releases

Results 7 mhddos_proxy issues
Sort by recently updated
recently updated
newest added

### Application config file overriding defaults Kindly suggest to consider including application-wide config file. Number of command-line options has inclreased, and personally for me it's more comfortable to handle them...

Good day MHDDoS team! If you remember, I created localization for the project. I closely watched the discussion about recent changes in the project, and I already said, my opinion...

Colleagues, I was checking out open problems, and I found at least 3 of them may require the common underlying functionality: porthole-ascend-cinnamon/mhddos_proxy#191, porthole-ascend-cinnamon/mhddos_proxy#105, porthole-ascend-cinnamon/mhddos_proxy#107 require dynamic analysis of the ongoing...

When the async version is merged, we can leverage async architecture to run async HTTP server (optionally) to provide information about status of the attack, targets, and stats as JSON...

enhancement
help wanted

Instead of doing `randbytes` on each request, it's better to pre-allocate a few random Mb in a shared memoryview and loop over them (e.g. by moving index with +1 offset...

enhancement
help wanted

As of now the functionality of `TargetStats` is quite limited. Ideally we want to know much more. For example: * histogram for connection lifetime (better with per-stage markers, like TCP...

enhancement
help wanted

Async version only. As of now all proxy requests (for example, socks5 commands) are generated by creating Python objects (from `python_socks` library) and then generating bytes from them. Both operations...

enhancement
help wanted