-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 20/05/11 11:55, Jan Just Keijser wrote:
>> - From a quick brain storm, for --comp-lzo, the only compatible/valid
>> combinations are:
>>
>>Client Server
>>(no --comp-lzo) (no --comp-lzo)
>>--comp-lzo {,ad
Hi *,
David Sommerseth wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 16/05/11 13:10, David Sommerseth wrote:
This makes 'comp-lzo' pushable without requiring clients to have
--comp-lzo defined in the client configs. To make 'comp-lzo' not
pushable on the client, a new 'disabled'
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 16/05/11 13:10, David Sommerseth wrote:
> This makes 'comp-lzo' pushable without requiring clients to have
> --comp-lzo defined in the client configs. To make 'comp-lzo' not
> pushable on the client, a new 'disabled' argument have been added.
>
>
If you have a problem in what can or cannot be pushed to client, why
not do this generic?
Something like:
---
push-allowed="comp-lzo ..."
push-disallow="comp-lzo ..."
---
On Mon, May 16, 2011 at 2:10 PM, David Sommerseth wrote:
>
> This makes 'comp-lzo' pushable without requiring clients to have
This makes 'comp-lzo' pushable without requiring clients to have
--comp-lzo defined in the client configs. To make 'comp-lzo' not
pushable on the client, a new 'disabled' argument have been added.
Trac-ticket: 128
Signed-off-by: David Sommerseth
---
openvpn.8 | 12 ++--
options.c |