An important aspect to #8 was the 250ms lock, that allowed
you to send multiple requests while others were locked out.
First I was trying to send the requests from my local
machine, which made it nearly impossible to get usable
numbers because of the delay in the network.
Before I started using level2 machine to both send and
receive, I was planning to bind on every port of the
level2 server to stop/slow others thus raising my own
chances of hit. Luckily it didn't come to that.
Even before the port number attack, I was trying to find
a pattern in the request object pointer values in
subsequent backtraces. This gave me the port idea.
Also spent a few hours trying to exploit the Twisted HTTP
client by malformed HTTP redirects (taking the over-
specified Twisted version in the README as a clue).
Before I started using level2 machine to both send and receive, I was planning to bind on every port of the level2 server to stop/slow others thus raising my own chances of hit. Luckily it didn't come to that.
Even before the port number attack, I was trying to find a pattern in the request object pointer values in subsequent backtraces. This gave me the port idea.
Also spent a few hours trying to exploit the Twisted HTTP client by malformed HTTP redirects (taking the over- specified Twisted version in the README as a clue).