Note:
Starting with openvpn 2.3.0 there seem to be changes how plugins are enabled
and there are configure switches now for disabling the shipped plugins.
Note:
Starting with openvpn 2.3.0 there seem to be changes how plugins are enabled
and there are configure switches now for disabling the shipped plugins.
Note:
This commit is improving the openvpn package to build the included
plugins if possible (currently only the pam authentication plugin
if pam is installed), but also introducing the 'plugins_enabled'
variable within the openvpn.conf file which can be used to define
a space seperated list of plugins which should be build additionally.
This will offer a convinient way for targets which patch in custom
plugins to enable them within the build process of the package.
The only thing to do is to append the desired plugin to then list
stored within the $plugins_enabled variable.
Example: Adding 'myplugin' within a target specific 'openvpn.conf'
--------------------------------------------------------------------
var_append plugins_enabled ' ' "myplugin"
--------------------------------------------------------------------
(maybe we should implement a Config option later because it mostly
just have sense on openvpn servers)
* improved openvpn to use the commands provided by iproute2 if
available instead of using the depreceated ifconfig)
git-svn-id: svn://svn.opensde.net/opensde/package/trunk@20196 10447126-35f2-4685-b0cf-6dd780d3921f