Re: USE_QUIC=1 support for awslc

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: Managing haproxy configs at scale

On 23/01/2024 22:44, Zach Pearson wrote: Hello, We are using haproxy in a few different environments/functions and the configurations are getting complicated to manage. We are already using Jinja2 to generate environment specific configs but was wondering if anyone has suggestions on tools or

Managing haproxy configs at scale

Hello, We are using haproxy in a few different environments/functions and the configurations are getting complicated to manage. We are already using Jinja2 to generate environment specific configs but was wondering if anyone has suggestions on tools or processes we can adopt to help us manage o

Re: USE_QUIC=1 support for awslc

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: HAProxy Technologies NERC CIP 13 Vendor Questionnaire

On Tue, Jan 23, 2024 at 12:11:56PM +0100, ??? wrote: > how can HAProxy be related, for example, to "NERC requires CORE to revoke > access within 24 hours when remote or onsite > access is no longer needed by your personnel to CORE systems or > facilities." ? Ilya, please avoid responding

Re: HAProxy Technologies NERC CIP 13 Vendor Questionnaire

how can HAProxy be related, for example, to "NERC requires CORE to revoke access within 24 hours when remote or onsite access is no longer needed by your personnel to CORE systems or facilities." ? вт, 23 янв. 2024 г. в 00:58, Robert Dillabough : > Hi Support, > > For NERC compliance, CORE need