I had reported the problem a few months ago and was told that it was
already gone from 2.1. Didn't check myself though.
> Oh and plenty of folks run linux socks5 so I would assume theres a small user
> space mode
It breaks UDP with socks5, TCP is not affected. Since most applications
don't use UDP, it may well have gone unnoticed. The problem is that
with the bug it is impossible to tell from user space whether a socket
is unbound or bound to 127.0.0.1. (other than tracking the socket(2)
call, which libsocks5 doesn't do).
olaf