On Fri, Jan 26, 2018 at 1:22 AM, Igor Cicimov < ig...@encompasscorporation.com> wrote:
> Hi Lukas, > > On Fri, Jan 26, 2018 at 1:04 AM, Lukas Tribus <lu...@ltri.eu> wrote: > >> Hello, >> >> >> On 25 January 2018 at 14:53, Igor Cicimov >> <ig...@encompasscorporation.com> wrote: >> > >> > Hi, >> > >> > The info below, that openssl version fort he build is little bit oldish >> isn't it? >> > >> > # haproxy -vv >> > [...] >> > Built with OpenSSL version : OpenSSL 1.0.1f 6 Jan 2014 >> > Running on OpenSSL version : OpenSSL 1.0.1f 6 Jan 2014 >> > [...] >> >> >> ALPN requires OpenSSL 1.0.2. You are using Ubuntu Trusty, which ships >> OpenSSL 1.0.1. >> >> > Ok, so > > >> >> >> > # openssl version >> > OpenSSL 1.1.0g 2 Nov 2017 >> >> > I have even more recent openssl version and this should work. > > >> >> Don't know where that's from, but not from a vanilla Ubuntu trusty >> installation. >> >> > You mean where that 1.0.1f came from? Obviously the installed one is > 1.1.0g and why does it matter where it came from? Where is haproxy looking > for openssl? Maybe I'm missing some library links ... > > >> >> Upgrade to the *current* LTS release, which is Ubuntu Xenial. It ships >> OpenSSL 1.0.2. >> > > For sure I don't have to update the whole distro to get the newest > openssl :-) > > >> >> >> Lukas >> > > Or you meant using the haproxy 16.04 image actually. Ok, another option is to compile it myself with the openssl version I have atm.