Re: USE_QUIC=1 support for awslc

2024-01-24 Thread Frederic Lecaille
On 1/24/24 05:58, Yaacov Akiba Slama wrote: > So right now, the only thing missing in aws_lc in order to fully support > quic is the implementation of EVP_chacha20() ? This is one of the *identified* things which are missing in addition to TLS_AES_128_CCM_SHA256 which cannot be enabled. This does

Re: USE_QUIC=1 support for awslc

2024-01-23 Thread Yaacov Akiba Slama
So right now, the only thing missing in aws_lc in order to fully support quic is the implementation of EVP_chacha20() ? Thanks a lot for your work, --yas On 23/01/2024 17:18, Frederic Lecaille wrote: FYI, I have just pushed 4 patches to master to make haproxy support 0-RTT when built against aw

Re: USE_QUIC=1 support for awslc

2024-01-23 Thread Frederic Lecaille
On 1/15/24 17:16, Yaacov Akiba Slama wrote: > On 04/10/2023 18:38, William Lallemand wrote: >> Hello, >> >> I fixed the build for USE_QUIC=1 and AWSLC which is limited like Ilya >> mentionned. >> >> For now: >> >>     - 0RTT was disabled. >>     - TLS1_3_CK_CHACHA20_POLY1305_SHA256, TLS1_3_CK_AES_1

Re: USE_QUIC=1 support for awslc

2024-01-17 Thread Frederic Lecaille
On 1/17/24 00:53, Hopkins, Andrew wrote: > AWS-LC recently plumbed support for ChaChaPoly and AES CCM through the > existing EVP_CIPHER API that HAProxy uses in > https://github.com/aws/aws-lc/pull/1311 and > https://github.com/aws/aws-lc/pull/1373. Do you need support for just the > cipher EVP

Re: USE_QUIC=1 support for awslc

2024-01-16 Thread Hopkins, Andrew
AWS-LC recently plumbed support for ChaChaPoly and AES CCM through the existing EVP_CIPHER API that HAProxy uses in https://github.com/aws/aws-lc/pull/1311 and https://github.com/aws/aws-lc/pull/1373. Do you need support for just the cipher EVP_chacha20? On 1/16/24, 5:30 AM, "Frederic Lecaill

Re: USE_QUIC=1 support for awslc

2024-01-16 Thread Frederic Lecaille
On 1/16/24 14:25, Frederic Lecaille wrote: > On 1/15/24 17:16, Yaacov Akiba Slama wrote: >> On 04/10/2023 18:38, William Lallemand wrote: >>> Hello, >>> >>> I fixed the build for USE_QUIC=1 and AWSLC which is limited like Ilya >>> mentionned. >>> >>> For now: >>> >>>     - 0RTT was disabled. >>>   

Re: USE_QUIC=1 support for awslc

2024-01-16 Thread Frederic Lecaille
On 1/15/24 17:16, Yaacov Akiba Slama wrote: > On 04/10/2023 18:38, William Lallemand wrote: >> Hello, >> >> I fixed the build for USE_QUIC=1 and AWSLC which is limited like Ilya >> mentionned. >> >> For now: >> >>     - 0RTT was disabled. >>     - TLS1_3_CK_CHACHA20_POLY1305_SHA256, TLS1_3_CK_AES_1

Re: USE_QUIC=1 support for awslc

2024-01-16 Thread Frederic Lecaille
On 1/15/24 17:16, Yaacov Akiba Slama wrote: > On 04/10/2023 18:38, William Lallemand wrote: >> Hello, >> >> I fixed the build for USE_QUIC=1 and AWSLC which is limited like Ilya >> mentionned. >> >> For now: >> >>     - 0RTT was disabled. >>     - TLS1_3_CK_CHACHA20_POLY1305_SHA256, TLS1_3_CK_AES_1

Re: USE_QUIC=1 support for awslc

2024-01-15 Thread Yaacov Akiba Slama
On 04/10/2023 18:38, William Lallemand wrote: Hello, I fixed the build for USE_QUIC=1 and AWSLC which is limited like Ilya mentionned. For now: - 0RTT was disabled. - TLS1_3_CK_CHACHA20_POLY1305_SHA256, TLS1_3_CK_AES_128_CCM_SHA256 were disabled https://github.com/aws/aws-lc/commit/

USE_QUIC=1 support for awslc

2023-10-04 Thread William Lallemand
Hello, I fixed the build for USE_QUIC=1 and AWSLC which is limited like Ilya mentionned. For now: - 0RTT was disabled. - TLS1_3_CK_CHACHA20_POLY1305_SHA256, TLS1_3_CK_AES_128_CCM_SHA256 were disabled - clienthello callback is missing, certificate selection could be limited (RSA + ECD