![]() ![]() Regardless of the OpenVPN developers decision not to include the patch in OpenVPN, the patch is attractive because it is so easy to implement: simply apply the patch to both the OpenVPN server and the OpenVPN client and add a single, identical option to the configuration files for each. ![]() OpenVPN developers again explained why they do not want to include the patch in OpenVPN and discussed alternatives. In December 2016, further discussion took place on the OpenVPN users mailing list. "To avoid confusing users further going for a possibly insecure setup, this thread will be locked now." "For more information, have a look at these URLs It is called obfsproxy and can be used together with OpenVPN without needing any re-compilation of OpenVPN. "And we especially discourage using such an approach when there exists a far better solution, used by the TOR community. The discussion has been removed, but the last post was: "We (OpenVPN developers) do not encourage people building their own versions of OpenVPN changing the wire-protocol like this, without the patch being through a proper patch review and having evaluated possible security risks related to such a change. There was a long discussion of the patch on the OpenVPN Community Support Forum. ![]() However, the patch is controversial: it was not accepted as an addition to OpenVPN by the OpenVPN developers. ![]() The option "scrambles" each buffer of traffic before it is sent between the OpenVPN client and server. The option can be useful to avoid having OpenVPN traffic detected by monitoring or censoring mechanisms such as the Great Firewall of China. The Patch as Modified for Use in TunnelblickĪ patch to add a "scramble" option to OpenVPN was proposed in April, 2013. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |