> > > > Thanks, this change makes sense. I have not actively tried to provoke > it (like, by connecting to a "fake SOCKS server" that will trigger it), > but the change is obviously an improvement to "if it's not ==1, it > must be a TCP error!"). >
An easy way to "provoke" this is to use openssh proxy (say, -D 1080) and use it to proxy to a udp server. SSH will close the connection as it does not support udp association. Probably it should return one of the socks5 error code instead, but doesn't. Even if it did, our recv_socks_reply() is not capable of handling such errors. Selva
_______________________________________________ Openvpn-devel mailing list Openvpn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-devel
