obfsproxy: obfs2 server sends handshake message on client connection
obfsproxy/obfs2 servers send their handshake message right after receiving a connection from a client.
It might make more sense to do the server handshake, after receiving the client's handshake message, because: a) it's more intuitive (?) b) the obfs2 spec says so c) it's less fingerprintable.
All these arguments are not very convincing, but in any case I prepared a patch for this issue.
If we decide to not apply this patch, we should update the obfs2 spec to not say
and the responder replies with: