id summary reporter owner description type status priority milestone component version severity resolution keywords cc 377 socks proxy always advertise authentication even if no authentication is provided by user irregulator Gert Döring "When trying to use OpenVPN with socks-proxy, OpenVPN client sends as acceptable methods both ""no authentication"" and ""plaintext authentication"". This can cause problem when user doesn't want to use any authentication at all. Since OpenVPN advertises both methods disregarding if user has an authentication file, if socks proxy picks plaintext authentication method, connection will fail. This is implemented in https://github.com/OpenVPN/openvpn/blob/master/src/openvpn/socks.c#L194. This problem came up when I tried to connect OpenVPN and obfsproxy, a socks proxy that obfuscates traffic and is used for Tor pluggable transports. Although I don't want to use any authentication, OpenVPN client will advertise plaintext authentication as available, and that method will be choosed by obfsproxy, causing the connection to drop. Yawning gives a better explanation and kindly provided a patch : https://github.com/OpenVPN/openvpn/pull/14 Please review." Patch submission closed major release 2.3.4 Networking OpenVPN 2.2.2 (Community Ed) Not set (select this one, unless your'e a OpenVPN developer) fixed