tteras/strongswan/testing/tests/sql/ip-split-pools-db/hosts, branch mastertteras' strongSwan tree
https://git-old.alpinelinux.org/user/tteras/strongswan/atom?h=master2017-11-15T16:09:55Ztesting: Globally define logging via syslog for charon-systemd2017-11-15T16:09:55ZTobias Brunnertobias@strongswan.org2017-11-10T14:53:52Zurn:sha1:be214cb17e4eead2e3260dfe4700939756f4734a
We could make the same change for charon (actually setting it for charon
in strongswan.conf.testing would work for charon-systemd too), however,
there are dozens of test cases that currently set charondebug in
ipsec.conf.
testing: Converted sql to systemd2017-11-11T15:41:15ZAndreas Steffenandreas.steffen@strongswan.org2017-11-11T06:18:51Zurn:sha1:323f0b05d75e828b72a0eb7b8d90bc1dd3823b69testing: attr-sql is a charon plugin2016-03-05T14:53:22ZAndreas Steffenandreas.steffen@strongswan.org2016-03-05T14:53:22Zurn:sha1:07b0eac4b12c7d164a3f347aa3d40c786a3cd1d4libhydra: Remove empty unused library2016-03-03T16:36:11ZTobias Brunnertobias@strongswan.org2016-02-12T15:35:54Zurn:sha1:28649f6d91971e0fe50078aec2937010e8c61cd8testing: Use absolute path to the _updown script in SQL scenarios2016-02-17T11:00:20ZTobias Brunnertobias@strongswan.org2016-02-17T10:55:45Zurn:sha1:4625113b1afa14afd916fd0f309a25cc7855490b
/usr/local/sbin is not included in PATH set by the charon init script and
since the ipsec script is obsolete when using swanctl it makes sense to
change this anyway.
testing: Change sql scenarios to swanctl2016-01-03T05:28:48ZAndreas Steffenandreas.steffen@strongswan.org2015-12-28T03:15:27Zurn:sha1:9db530493fd449795dfd48b2ae07a909ce50e377testing: Reduce runtime of all tests that use SQLite databases by storing them in ramfs2015-11-09T14:18:39ZTobias Brunnertobias@strongswan.org2015-11-06T16:27:45Zurn:sha1:10051b01e9a5accf004f861e7de8486304a550catesting: Updated certificates and keys in sql scenarios2014-10-06T07:42:58ZAndreas Steffenandreas.steffen@strongswan.org2014-10-06T07:42:58Zurn:sha1:100c1a4bf1f59414af8a1bfb6acb14b1a98e3349configure: Load fetcher plugins after crypto base plugins2014-09-24T15:34:54ZMartin Willimartin@revosec.ch2014-09-24T10:24:13Zurn:sha1:44b6a34d438f15dbafdf3a0bc58ed23ca0b08923
Some fetcher plugins (such as curl) might build upon OpenSSL to implement
HTTPS fetching. As we set (and can't unset) threading callbacks in our
openssl plugin, we must ensure that OpenSSL functions don't get called after
openssl plugin unloading.
We achieve that by loading curl and all other fetcher plugins after the base
crypto plugins, including openssl.
removed plutostart parameter2012-06-13T19:19:05ZAndreas Steffenandreas.steffen@strongswan.org2012-06-13T19:19:05Zurn:sha1:daa857029f85dab932e0f1674cee4504134dd751