tor-socksproto needs precise reading to avoid RPC mis-eaten data bug

We have decided to merge this anyway.

This should be fixed at the same time as #1590 (closed), but it's more serious than that bug - it's a race that could cause malfunctions.