Fix: server was timing out response from the proxy instead of the request from the client.

[notsure2]

This fixes a very annoying subtle bug, where the timeout was flipped on the client side in case of TCP only. So in case of a server resource that replies with empty TCP ACKs when receiving input (eg: idle SSH session sending SSH null packets to keep the connection alive), cloak was timing out the connection and killing it.

[cbeuw]

The original behaviour was that the stream times out when the proxy client hasn't sent any data to Cloak for a period of time (i.e. nothing was read from localConn). When the server is not sending anything to the stream, Cloak client doesn't time it out because there's no timeout on reading from stream

[cbeuw]

The scenario you mentioned may affect the server side:

Cloak/cmd/ck-server/ck-server.go

Lines 185 to 186 in e2c234f

	go util.Pipe(localConn, newStream, 0)
	go util.Pipe(newStream, localConn, sta.Timeout)

Because nothing is read from the proxy server program through localConn, Cloak closes that stream

[notsure2]

@cbeuw You are correct, I got confused because Pipe is dst, src, timeout instead of src, dst, timeout.
Please check now :-)