tteras/strongswan - tteras' strongSwan tree

	Commit message (Collapse)	Author	Age	Files	Lines
*	Allow more than one CERTREQ payload for IKEv2	Tobias Brunner	2013-02-08	1	-2/+2
\| \| \| \| \| \|	There is no reason not to do so (RFC 5996 explicitly mentions multiple CERTREQ payloads) and some implementations seem to use the same behavior as had to be used with IKEv1 (i.e. each CA in its own CERTREQ payload).
*	Add message rules to properly handle IKE fragments	Tobias Brunner	2012-12-24	1	-0/+8
\| \| \| \| \|	These are sent in unencrypted messages and are the only payload contained in such messages.
*	Reset the encrypted flag when handling IKE messages that contain a fragment	Tobias Brunner	2012-12-24	1	-0/+6
\| \| \| \| \|	Racoon sets the encrypted bit for messages containing a fragment, but these messages are not really encrypted (the fragmented message is though).
*	Add support for draft-ietf-ipsec-nat-t-ike-03 and earlier	Volker Rümelin	2012-12-19	1	-0/+12
\| \| \| \| \|	This adds support for early versions of the draft that eventually resulted in RFC 3947.
*	Increase the limit of acceptable IKEv1 CERTREQ payloads to 20	Martin Willi	2012-10-24	1	-1/+1
\|
*	Don't print hexdumps on loglevel 1 if hash verification fails	Martin Willi	2012-07-20	1	-3/+3
\|
*	Cleaned up memory management and return values for encryption payload	Martin Willi	2012-07-16	1	-14/+11
\|
*	Add a return value to keymat_v1_t.{get,update,confirm}_iv	Martin Willi	2012-07-16	1	-9/+36
\|
*	Use a bool return value in keymat_v1_t.get_hash_phase2()	Martin Willi	2012-07-16	1	-4/+2
\|
*	Store the major IKE version on ike_sa_id_t.	Tobias Brunner	2012-03-20	1	-0/+1
\|
*	Print IKEv1 notify types in message summary	Martin Willi	2012-03-20	1	-1/+2
\|
*	Support IKEv1 notifies in message_t.get_notify()	Martin Willi	2012-03-20	1	-1/+2
\|
*	Accept unencrypted Aggressive Mode messages.	Tobias Brunner	2012-03-20	1	-1/+2
\| \| \| \|	Racoon does not encrypt the third message during Aggressive Mode.
*	Encrypt payloads of third aggressive mode message	Martin Willi	2012-03-20	1	-3/+3
\|
*	Cast keymat safely, not based on external input	Martin Willi	2012-03-20	1	-36/+44
\|
*	Accept NULL as keymat when generating a message	Martin Willi	2012-03-20	1	-4/+10
\|
*	Separated libcharon/sa directory with ikev1 and ikev2 subfolders	Martin Willi	2012-03-20	1	-1/+1
\|
*	Another set of cleanups in message.c	Martin Willi	2012-03-20	1	-18/+19
\|
*	Some coding style cleanups	Martin Willi	2012-03-20	1	-3/+6
\|
*	Do not trust unprotected INFORMATIONALS, just print that we got one	Martin Willi	2012-03-20	1	-13/+18
\|
*	Remove executable flag from source code files	Martin Willi	2012-03-20	1	-0/+0
\|
*	Encrypt INFORMATIONAL exchange if needed	Clavister OpenSource	2012-03-20	1	-11/+22
\|
*	Handle incoming delete messages	Clavister OpenSource	2012-03-20	1	-0/+25
\|
*	certificate handling for XAuth responder.	Clavister OpenSource	2012-03-20	1	-2/+2
\|
*	IKEv1: Added basic support for INFORMATIONAL exchange types, and for ↵	Clavister OpenSource	2012-03-20	1	-9/+13
\| \| \| \|	NOTIFY_V1 messages in the 3rd message in quick_mode.
*	Message rules for IKEv1 NAT-T payloads added.	Tobias Brunner	2012-03-20	1	-0/+17
\|
*	Added payloads for IKEv1 NAT-Traversal negotiation.	Tobias Brunner	2012-03-20	1	-1/+1
\|
*	Handle invalid IKEv1 hashes more specifically.	Tobias Brunner	2012-03-20	1	-1/+1
\|
*	Handle unsupported IKEv1 exchange types more specifically.	Tobias Brunner	2012-03-20	1	-1/+1
\|
*	Handle INFORMATIONAL_V1 messages when no keys have been derived yet.	Tobias Brunner	2012-03-20	1	-2/+3
\| \| \| \| \| \| \| \|	This allows to gracefully process the INFORMATIONAL_V1 message rules which require the payloads to be encrypted and thus the exchange to be authenticated with a HASH payload. If such an exchange is now initiated before the ISAKMP_SA is established, the message is simply sent unencrypted and without HASH payload.
*	Fixed encryption of IKEv2 messages.	Tobias Brunner	2012-03-20	1	-2/+2
\|
*	Print message payload names after prepending IKEv1 HASH payload	Martin Willi	2012-03-20	1	-2/+2
\|
*	Authenticate and verify Phase 2 IKEv1 messages with appropriate hashes.	Tobias Brunner	2012-03-20	1	-2/+44
\|
*	Merged IKEv1 attribute payload/data into configuration payload/attribute	Martin Willi	2012-03-20	1	-5/+5
\|
*	IKEv1 ConfigMode: Added TRANSACTION exchange type. Added attribute_payload ↵	Clavister OpenSource	2012-03-20	1	-0/+26
\| \| \| \|	(IKEv2 equiv cp_payload) and data_attribute (IKEv2 equiv configuration_attribute) payload types. Did not combine with IKEv2 because it wasn't trivial to do so. This might be a task worth investigating in the future, because there is a decent amount of shared code here.
*	Set flags on message according to IKE version when parsing header.	Tobias Brunner	2012-03-20	1	-2/+8
\|
*	Encrypt IKEv1 messages.	Tobias Brunner	2012-03-20	1	-17/+66
\|
*	Decrypt IKEv1 messages.	Tobias Brunner	2012-03-20	1	-3/+43
\|
*	Provide keymat_t to message_t to encrypt/decrypt data.	Tobias Brunner	2012-03-20	1	-7/+8
\|
*	Print message ID as unsigned integer	Martin Willi	2012-03-20	1	-1/+1
\|
*	Added message encoding rules for quick mode	Martin Willi	2012-03-20	1	-0/+65
\|
*	Don't clone chunk in message.get_packet_data	Martin Willi	2012-03-20	1	-1/+1
\|
*	Added IKEv1 support to notify payload	Martin Willi	2012-03-20	1	-11/+18
\|
*	Don't set IKEv2 only header flags when using IKEv1	Martin Willi	2012-03-20	1	-3/+6
\|
*	Compile error fixed.	Tobias Brunner	2012-03-20	1	-1/+2
\|
*	Message parsing slightly refactored, allows parsing of unencrypted IKEv1 ↵	Tobias Brunner	2012-03-20	1	-40/+52
\| \| \| \|	messages.
*	Allow creation of message_t objects for IKEv1 packets.	Tobias Brunner	2012-03-20	1	-20/+32
\|
*	Certificate request payloads can be sent in pretty much any IKEv1 message.	Tobias Brunner	2012-03-20	1	-5/+18
\|
*	Message rules for IKEv1 INFORMATIONAL exchange added.	Tobias Brunner	2012-03-20	1	-0/+24
\| \| \| \| \|	Since INFORMATIONAL "exchanges" are actually unidirectionally sent message we don't have any responder rules.
*	Message rules for IKEv1 AGGRESSIVE exchange added.	Tobias Brunner	2012-03-20	1	-0/+72
\| \| \| \| \|	These are basically the same as for ID_PROT but no payloads are expected to be encrypted (at least if using PSK or signatures for authentication).