Hi!

It's me again - author of the eduVPN client for Windows. This time I have a 
new problem. And, a solution I'd like to share with OpenVPN community.

I am considering bundling openvpn.exe, openvpnserv.exe, and standard TAP 
drivers with eduVPN client to allow some degree of independence from stock 
OpenVPN installations.

However, our version of openvpnserv.exe should have some modifications 
(different named pipe, different registry key) to avoid collision with stock 
OpenVPN installation. But that's our long term goal.

Unfortunately, maintaining a mingw build environment for our own OpenVPN 
binaries is an overkill. Therefore, in the first stage, I have updated the 
Microsoft Visual Studio C++ project files to be able to compile 
openvpnserv.exe again:
- Project files were updated to Microsoft Visual Studio C++ 2017 Community 
Edition.
- Some minor updates were made to .h/.c files to compile using MSVC again.
- Support for x64 platform was added.
- All MSVC warnings were addressed and fixed.

Can I deliver the patches for above?

Best regards,
Simon Rozman

Attachment: smime.p7s
Description: S/MIME cryptographic signature

------------------------------------------------------------------------------
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

Reply via email to