Tunnelblick created a patch for openVPN client and server which can
hide your openVPN traffic from
deep packet inspection.
According to tunnelblicks-
an open source VPN provider for MacOSX The option can be useful to avoid having OpenVPN traffic detected by monitoring or censoring mechanisms such as the Great Firewall of China. The option "scrambles" each buffer of traffic before it is sent between the OpenVPN client and server.
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. Using obfsproxy is more complicated because it involves running another, separate program on both the server and the client.
But openVPN developer refused to add this. According to them
we especially discourage using such an approach when there exists a far better solution, used by the TOR community. It is called obfsproxy and can be used together with OpenVPN without needing any re-compilation of OpenVPN.
My question is you already know that Tor is slow and when it is used with pluggable transport like obfsproxy or meek it becomes slower. Now openVPN developers also want us to use this then don't you think by adding a obfsproxy server, VPN will become slower as Tor? How is it a far better option?Is there any security reason they refused to add this?
Full article source can be read
here
I've also asked this same question on
tor-stack exchange community but i didn't get a straight answer.
