[Openvpn-devel] Topics for the community meeting (Wed, 4th Apr 2018)

Hi, We're going to have an IRC meeting starting at 11:30 CET (10:30 UTC) on #openvpn-meeting irc.freenode.net. You do not have to be logged in to Freenode to join the channel. Current topic list along with basic information is here:

[Openvpn-devel] [PATCH] man: Improve token based authentication

Be more explicit that --auth-gen-token is to be considered a workaround for authentication scripts/plug-ins not supporting --auth-token. Also be more explicit that invalidated --auth-token values will result in the client disconnecting. Signed-off-by: David Sommerseth --- doc/openvpn.8 | 32 +++

[Openvpn-devel] Summary of the community meeting (Wed, 4th Apr 2018)

Hi, Here's the summary of the IRC meeting. --- COMMUNITY MEETING Place: #openvpn-meeting on irc.freenode.net Date: Wednesday 4th Apr 2018 Time: 11:30 CET (10:30 UTC) Planned meeting topics for this meeting were here: The next meet

Re: [Openvpn-devel] [PATCH] man: Improve token based authentication

Hi, On Wed, Apr 4, 2018 at 8:13 AM, David Sommerseth wrote: > Be more explicit that --auth-gen-token is to be considered a workaround > for authentication scripts/plug-ins not supporting --auth-token. > > Also be more explicit that invalidated --auth-token values will result > in the client disco

Re: [Openvpn-devel] [PATCH] man: Improve token based authentication

On 04/04/18 16:24, Selva Nair wrote: > Hi, > > On Wed, Apr 4, 2018 at 8:13 AM, David Sommerseth wrote: >> Be more explicit that --auth-gen-token is to be considered a workaround >> for authentication scripts/plug-ins not supporting --auth-token. >> >> Also be more explicit that invalidated --auth

[Openvpn-devel] [PATCH] Send authentication failure reason between plugins

This patch implements support for sending an authentication failure reason from a server plugin to a client plugin. Currently this can only be done using the management interface. To allow this to be done through the use of plugins, two changes were made. The first change is to allow a plugin to s

Re: [Openvpn-devel] [PATCH] Send authentication failure reason between plugins

On 04/04/18 16:43, Janito Vaqueiro Filho wrote: > This patch implements support for sending an authentication failure > reason from a server plugin to a client plugin. Currently this can only > be done using the management interface. To allow this to be done through > the use of plugins, two change

[Openvpn-devel] [PATCH v3] Revert to original password authentication after failed auth-token

Auth-tokens can expire. For by reconnecting when the server uses auth-gen-toke. Behaviour of OpenVPN client is to never fallback to the previous authentication method and continue using the auth-token. Depending on auth-retry it either quit or tried endlessly with an expired token. Since auth-gen-

[Openvpn-devel] [PATCH v4] Revert to original password authentication after failed auth-token

Auth-tokens can expire. For by reconnecting when the server uses auth-gen-toke. Behaviour of OpenVPN client is to never fallback to the previous authentication method and continue using the auth-token. Depending on auth-retry it either quit or tried endlessly with an expired token. Since auth-gen-

[Openvpn-devel] [PATCH] Send authentication failure reason between plugins

This patch implements support for sending an authentication failure reason from a server plugin to a client plugin. Currently this can only be done using the management interface. To allow this to be done through the use of plugins, two changes were made. The first change is to allow a plugin to s