Re: [Openvpn-devel] rfc: mingw and the interactive service code

Hi, On Wed, Jan 27, 2021 at 10:04:49PM -0500, Selva Nair wrote: > I see two options: > (i) force __USE_MINGW_ANSI_STDIO = 0 in configure. > (ii) Change all stdio function calls to be compatible building with and > without this macro defined. AFICT, the only change required would be to > replace

[Openvpn-devel] rfc: mingw and the interactive service code

Hi, Starting version 8, mingw has started automatically setting __USE_MINGW_ANSI_STDIO = 1 under some feature-set conditions: for example, when _GNU_SOURCE is defined or -std=C99, both of which are true in our case. See: release notes at http://mingw-w64.org/doku.php This causes several stdio

[Openvpn-devel] [PATCH 2/2] More explicit versioning compatibility in sample-plugins/defer/simple.c

While not required, adding openvpn_plugin_min_version_required_v1 helps by making an example for others to copy, and helps to explicitly call attention to the difference between the API version number and the struct version number in v3 calls. --- sample/sample-plugins/defer/simple.c | 21

[Openvpn-devel] [PATCH 1/2] Update openvpn_plugin_func_v2 to _v3 in sample-plugins/defer/simple.c

This isn't strictly required, but it modernizes the functions used. This change makes _open the same parameter form as _func (for better parallelism in function writing) and includes a check for the correct struct version, as recommended by openvpn-plugin.h ---

Re: [Openvpn-devel] [PATCH] Support for wolfSSL in OpenVPN

Am 27.01.21 um 18:25 schrieb Juliusz Sosinowicz: > Hi Arne, > > I believe I fixed the issues that you mentioned in your review of the > patch for wolfSSL. I have sent a new patch tested on the latest master > branch on OpenVPN along with the version of wolfSSL found in this pull > request:

[Openvpn-devel] [PATCH applied] Re: Documentation fixes around openvpn_plugin_func_v3 in openvpn-plugin.h.in

Your patch has been applied to the master, release/2.5 and release/2.4 branch. (Thanks, David. I thought it looked good, but you have worked with the plugin API for much longer :-) ). commit 595be121b60f8cee9d4816172a7f9a4987560641 (master) commit c6013abe860e8c76e132e98458fef7122a1622c0

Re: [Openvpn-devel] [PATCH] Documentation fixes around openvpn_plugin_func_v3 in openvpn-plugin.h.in

On 25/01/2021 00:46, Greg Cox wrote: The comments refered to parameters found in openvpn_plugin_func_v2 but not in v3 --- include/openvpn-plugin.h.in | 12 ++-- 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/include/openvpn-plugin.h.in b/include/openvpn-plugin.h.in

[Openvpn-devel] [PATCH] Support for wolfSSL in OpenVPN

This patch adds support for wolfSSL in OpenVPN. Support is added by using wolfSSL's OpenSSL compatibility layer. Function calls are left unchanged and instead the OpenSSL includes point to wolfSSL headers and OpenVPN is linked against the wolfSSL library. The wolfSSL installation directory is

[Openvpn-devel] [openvpn-devel] Wiki Howto URL

Hi, in the Howto there was this URL: https://community.openvpn.net/openvpn/wiki/HOWTO#ExpandingthescopeoftheVPNtoincludeadditionalmachinesoneithertheclientorserversubnet. Note: There is a fullstop on the end. I changed this URL to:

[Openvpn-devel] Summary of the community meeting (27th January 2021)

Hi, Here's the summary of the IRC meeting. --- COMMUNITY MEETING Place: #openvpn-meeting on irc.freenode.net Date: Wed 27th January 2021 Time: 11:30 CET (10:30 UTC) Planned meeting topics for this meeting were here: Your local