Frederic Lecaille f5b09dc452 MINOR: quic: Token for future connections implementation. ... There exist two sorts of token used by QUIC. They are both used to validate the peer address (path validation). Retry are used for the current connection the client want to open. This patch implement the other sort of tokens which after having been received from a connection, may be provided for the next connection from the same IP address to validate it (or validate the network path between the client and the server). The token generation is implemented by quic_generate_token(), and the token validation by quic_token_chek(). The same method is used as for Retry tokens to build such tokens to be reused for future connections. The format is very simple: one byte for the format identifier to distinguish these new tokens for the Retry token, followed by a 32bits timestamps. As this part is ciphered with AEAD as cryptographic algorithm, 16 bytes are needed for the AEAD tag. 16 more random bytes are added to this token and a salt to derive the AEAD secret used to cipher the token. In addition to this salt, this is the client IP address which is used also as AAD to derive the AEAD secret. So, the length of the token is fixed: 37 bytes.		2024-08-30 17:04:09 +02:00
..
haproxy	MINOR: quic: Token for future connections implementation.	2024-08-30 17:04:09 +02:00
import	MAJOR: import: update mt_list to support exponential back-off (try #2)	2024-07-09 16:46:38 +02:00
make	BUILD: makefile: support USE_xxx=0 as well	2024-04-11 11:06:19 +02:00