strongswan/man
Tobias Brunner 190a278854 plugin-loader: Optionally use load option in each plugin section to load plugins
This now works because all plugins use the same config namespace.

If <ns>.load_modular is true, the list of plugins to load is determined
via the value of the <ns>.plugins.<name>.load options.

Using includes the following is possible:

charon {
  load_modular = yes
  plugins {
    include strongswan.d/charon/*.conf
  }
}

charon-cmd {
  load_modular = yes
  plugins {
    include strongswan.d/charon-cmd/*.conf
  }
}

Where each .conf file would contain something like:

<name> {
  load = yes
  <option> = <value>
}

To increase the priority of individual plugins load = <priority> can be
used (the default is 1).  For instance, to use openssl instead of the
built-in crypto plugins set in strongswan.d/charon/openssl.conf:

openssl {
  load = 10
}

If two plugins have the same priority their order in the default plugin
list is preserved.  Plugins not found in that list are ordered
alphabetically before other plugins with the same priority.
2014-02-12 14:34:33 +01:00
..
.gitignore Build generated man pages via configure script 2013-09-13 14:32:51 +02:00
Makefile.am Build generated man pages via configure script 2013-09-13 14:32:51 +02:00
ipsec.conf.5.in ike: Restart inactivity counter after doing a CHILD_SA rekey 2014-01-23 16:19:22 +01:00
ipsec.secrets.5.in Build generated man pages via configure script 2013-09-13 14:32:51 +02:00
strongswan.conf.5.in plugin-loader: Optionally use load option in each plugin section to load plugins 2014-02-12 14:34:33 +01:00