tteras/strongswan - tteras' strongSwan tree

	Commit message (Collapse)	Author	Age	Files	Lines
*	testing: Update test scenarios for Debian jessie	Tobias Brunner	2016-06-16	1	-2/+2
\| \| \| \| \| \| \|	The main difference is that ping now reports icmp_seq instead of icmp_req, so we match for icmp_.eq, which works with both releases. tcpdump now also reports port 4500 as ipsec-nat-t.
*	testing: Update TKM assert strings	Reto Buerki	2015-05-05	1	-2/+2
\|
*	testing: Update tkm/multiple-clients/evaltest.dat	Reto Buerki	2014-10-31	1	-2/+1
\| \| \| \| \| \|	Since the CC context is now properly reset in the bus listener plugin, the second connection from host dave re-uses the first CC ID. Adjust the expect string on gateway sun accordingly.
*	configure: Load fetcher plugins after crypto base plugins	Martin Willi	2014-09-24	2	-2/+2
\| \| \| \| \| \| \| \| \| \|	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.
*	testing: Update certs and keys in tkm tests	Reto Buerki	2014-09-17	1	-0/+0
\| \| \| \|	References #705.
*	charon-tkm: Update integration tests	Reto Buerki	2013-12-04	1	-0/+8
\|
*	Implement multiple-clients integration test	Reto Buerki	2013-03-19	12	-0/+158
	Two transport connections to gateway sun are set up, one from client carol and the other from client dave. The gateway sun uses the Trusted Key Manager (TKM) and is the responder for both connections. The authentication is based on X.509 certificates. In order to test the connections, both carol and dave ping gateway sun.