Hi Arne, On 28/10/16 13:08, Arne Schwabe wrote: > Hm, > > > I would like to see a rationale why this is needed. The client will > already only warn on unsupported options. Your patch would make push > "setenv opt unsupported" similar to "push unsupported". the rationale behind this is based on an email thread on openvpn-users:
if I can set setenv opt UNSUPPORTED=1 in a client config, then why can't I push that from the server? it would allow an admin to do stuff like push "setenv opt register-dns" which would apply only to the clients that support it (Windows) whereas no warnings are logged on other platforms. So it's more a way to suppress a warning message than anything else. In theory you could also use "pull-filter" for this but that would require a change on all clients (and it won't work in 2.3 clients). cheers, JJK ------------------------------------------------------------------------------ The Command Line: Reinvented for Modern Developers Did the resurgence of CLI tooling catch you by surprise? Reconnect with the command line and become more productive. Learn the new .NET and ASP.NET CLI. Get your free copy! http://sdm.link/telerik _______________________________________________ Openvpn-devel mailing list Openvpn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-devel
