Re: [Openvpn-devel] [PATCH] Added check for variable CONFIGURE_DEFINES into options.c

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/11/10 16:57, Samuli Seppänen wrote: > Applied to the feat_misc branch, to be merged into allmerged and beta2.2. commit 5682d3394204c788988b3cf67b3443a717704d2c Author: Samuli Seppänen List-Post:

Re: [Openvpn-devel] [PATCH 0/3] Code clean-up - removing "dead" code.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 28/08/10 22:31, David Sommerseth wrote: > This is a patch series which tries to do some source code clean-up. > After having noticed that ./configure --enable-pthread was simply doing > *nothing*, as it was forcefully being disabled in syshead.h, I

Re: [Openvpn-devel] [PATCH] Remove hardcoded path to resolvconf

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/11/10 01:22, Jesse Young wrote: > On Thu, Nov 11, 2010 at 00:25:03 +0100, David Sommerseth wrote: > On 01/11/10 17:33, Jesse Young wrote: Signed-off-by: Jesse Young --- contrib/pull-resolv-conf/client.down

Re: [Openvpn-devel] Variable common_name can be blank in client-connect script

No problem. I drop all together the username-as-common-name because it has other side effects on calling the client-disconnect script when a client reconnects (I sent another note on November 4th). As you mention, I now handle this logic in the client connect/authenticate scripts and is working

Re: [Openvpn-devel] Variable common_name can be blank in client-connect script

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/10/10 20:56, Carlos Soto wrote: > Author: Carlos Soto mailto:carlos.s...@terra.es>> > > Variable common_name can be blank in client-connect script > > If a server is configured with auth-user-pass-optional and > username-as-common-name it is