Re: AWS-LC : Incompatibilities and suggested config

Hello William, Le 13/02/2025 à 11:31, William Lallemand a écrit : Go is in fact not required, you only need it if you want to activate FIPS. You can compile like this: cmake -DCMAKE_BUILD_TYPE=Release -DBUILD_SHARED_LIBS=1 -DDISABLE_GO=1 -DDISABLE_PERL=1 \ -DBUILD_TESTING=0 -DCMAKE_INST

Re: AWS-LC : Incompatibilities and suggested config

Hello Artur, On Thu, Feb 13, 2025 at 12:19:40AM +0100, Artur wrote: > Subject: Re: AWS-LC : Incompatibilities and suggested config > Hello Willy and William, > > Thank you for your explanations and suggestions. > > I've checked the ciphers supported by aws-lc and w

Re: AWS-LC : Incompatibilities and suggested config

Hello Willy and William, Thank you for your explanations and suggestions. I've checked the ciphers supported by aws-lc and with help of Mozilla SSL Configuration Generator I have now a reasonable configuration for haproxy. As it may be of some interest, I post it here. I'm currently running h

Re: AWS-LC : Incompatibilities and suggested config

Sending this back, looks like I got block by the RBL again. On Wed, Feb 05, 2025 at 06:07:39PM +0100, Artur wrote: > Hello ! > > I'm testing aws-lc library with haproxy (3.1) and I was surprised to get a > start failure after migration from quictls to aws-lc : > > [ALERT] : config : parsing [/et

Re: AWS-LC : Incompatibilities and suggested config

Hello Artur, On Wed, Feb 05, 2025 at 06:07:39PM +0100, Artur wrote: > Hello ! > > I'm testing aws-lc library with haproxy (3.1) and I was surprised to get a > start failure after migration from quictls to aws-lc : > > [ALERT] : config : parsing [/etc/haproxy/haproxy.cfg:19] : unknown keyword > '