Hi Selva, We are considering distributing a local copy of OpenVPN with eduVPN Client: - To provide better app isolation; - To allow eduVPN to manage and update own OpenVPN copy.
The problem is one cannot run two openvpnserv.exe services at the same time, because the service control named pipe is hard-coded to "\\.\pipe\openvpn\service". While reviewing the openvpnserv.exe source code, I noticed on the other hand, that registry key is configurable as "HKEY_LOCAL_MACHINE\SOFTWARE\<PACKAGE_NAME>". Analogous to that, I have created a patch https://github.com/Amebis/openvpn/commit/103f07e54f8c672e1fa220ef197d26692c5d1300 to support "<PACKAGE_NAME>" configuration of named pipes as well. Along with https://github.com/Amebis/openvpn/commit/082e0c0de2d79ac61cae33128d8b35b392fba664 and https://github.com/Amebis/openvpn/commit/9084c4822b83ed77b7bedf938acb3d0dd8c3b382 patches to make OpenVPN Administrators group and OpenVPN firewall rule names configurable as well. Those three patches provide sufficient way for us to build and run a clone of openvpnserv.exe that would not collide with the original one, should user install the original OpenVPN on the same computer. 1. Do you think this commits are appropriate to get merged in the official OpenVPN source? (I can deliver git-send-email patches, of course.) 2. We would like to hear your expert opinion about this use-case. Any considerations, drawbacks and like? Thank you and best regards, Simon Rozman ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Openvpn-devel mailing list Openvpn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-devel
