Hi Erich, > I our build environment we are using a makefile which is calling the > original XSwan makefile passing all our relevant parameters.
When using strongSwan you should definitely use the provided ./configure script to modify any build settings. > The way I understand StrongSwan it is basically an IKEv1/2 daemon, so I > _believe_ there is just userland to be installed. Usually yes. strongSwan can use different IPsec backends; for Linux you should go for the Netlink based XFRM backend, which is used by default. > Is there a comprehensive list of configure parameters ( I don't refer to > that terse documentation from configure --help :-) ) That --help provides an overview over all options. If you are familiar with building autotools bases software that should be rather straight forward. For the first steps you should go with the default options, just adapt installation paths (--sysconfdir/--prefix/etc.) for your needs. At the end of your configure run, you get a list of plugins that have been selected for the build. Once you get a feeling about it, start to enable features you additionally need, and remove what you don't need. For example you can replace the various crypto plugins by a different backend, such as OpenSSL. A list of plugins is available at [1]. Regards Martin [1]http://wiki.strongswan.org/projects/strongswan/wiki/PluginList _______________________________________________ Users mailing list [email protected] https://lists.strongswan.org/mailman/listinfo/users
