6 Commits

Author	SHA1	Message	Date
Marten Seemann	73f7636537	use a random length destination connection ID on the Initial packet ... The destination connection ID on the Initial packet must be at least 8 bytes long. By using all valid values, we make sure that the everything works correctly. The server chooses a new connection ID with the Retry or Handshake packet it sends, so the overhead of this is negligible.	2018-07-03 18:01:41 +07:00
Marten Seemann	0bd7e744ff	implement parsing of headers with different connection ID lengths	2018-07-03 18:01:41 +07:00
Marten Seemann	fae32101a0	use different source and destination connection IDs	2018-04-23 15:23:01 +09:00
Marten Seemann	d47124d14d	add more methods to the protocol.ConnectionID ... This will make it easier to change the underlying type of the connection ID (potentially an array is faster than a byte slice).	2018-04-19 16:08:06 +09:00
Marten Seemann	1a035a265c	change the type of Connection ID to byte slice	2018-04-18 22:41:24 +09:00
Marten Seemann	af8971d8c9	move connection ID generation from the utils to the protocol package	2018-04-17 20:21:06 +09:00