You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Unlike other http-tunnels, Tunna generates a tcp connection for each request and response, And this is very good, Because it simulates a real http queries.
Most of http tunnels generate only one TCP connection, And all TCP-traffics are exchanged through it.
Is there any settings to choise traffics will be transmitted through one TCP-connection or multiple connections?! (however generating a tcp connection for each request and response is better solution, but maybe one TCP-connection faster than multiple connections)
The text was updated successfully, but these errors were encountered:
If I understand this correctly, you mean why not use multiple connections to the server. Mainly this is because of design decisions, at the time of writing this tool (back in 2014), I wanted it to be as stealth as possible and not to rely on the webserver as much.
One of the reasons was the php webshell that stalls a thread to keep the connection alive, at the time I was thinking that overusing this could run the webserver out of resources.
The other reason was that this was made as a hacking tool, was not thinking of other uses (at the time). Point is, that now this is so deep embedded in the code base that it is almost impossible to change.
If I had to do it again I would have done it differently :)
Unlike other http-tunnels, Tunna generates a tcp connection for each request and response, And this is very good, Because it simulates a real http queries.
Most of http tunnels generate only one TCP connection, And all TCP-traffics are exchanged through it.
Is there any settings to choise traffics will be transmitted through one TCP-connection or multiple connections?! (however generating a tcp connection for each request and response is better solution, but maybe one TCP-connection faster than multiple connections)
The text was updated successfully, but these errors were encountered: