On Thu, Apr 9, 2009 at 6:03 AM, Karl O. Pinc <k...@meme.com> wrote: > It occurs to me that if I want to do more than > beg I should submit a patch, so one is attached. > > On 04/08/2009 05:46:46 PM, Alon Bar-Lev wrote: >> >> Available as part of OpenSC build [1]. >> >> [1] http://www.opensc-project.org/build > > I noticed that. Does that build all of what > OpenVPN 2.1 packages for Windows, i.e. includes > OpenVPN GUI? The project does not seem to release > binaries for OpenVPN GUI, which is a requirement > for me.
OpenVPN GUI is an application that is not part of OpenVPN. The fact that it is provided within the same installer is a mistake in my view. It also does not working in many scenarios OpenVPN support as it does not use the management interface. The tap also is not provided as it also should have been provided by a different package, as it is too being used by other projects, such as coLinux. > I was also a little put off by: > "The OpenVPN overlay is provided in order to solve OpenSSL version > incompatibility between OpenSC and OpenVPN projects." > How can I make sure that I've got what OpenVPN is releasing > so that I can go to OpenVPN for support? As OpenSSL does not have stable ABI, compiling two projects with different versions of OpenSSL, and loading the two into the same process results in invalid behavior. > The OpenVPN devs have a "built" source tree in which they run > install-win32/buildinstaller. My point being that > if they would package it up > and release it alongside the resultant installer > none of these sorts of issues would ever come up. Wrong. Alon.
