Few additional notes: You could also set OPENSSL_HOME env variable to the specific folder with the valid openssl binaries.
вт, 8 нояб. 2022 г. в 13:01, Entwicklung <entwickl...@giftinfo.uni-mainz.de >: > Hello Stephen, > > so it‘s on my responsibility to install the correct version. > > Thank you for your quick answer. > > Guido > > > > *Von:* Stephen Darlington <stephen.darling...@gridgain.com> > *Gesendet:* Dienstag, 8. November 2022 10:56 > *An:* user <user@ignite.apache.org> > *Betreff:* Re: Ignite OpenSSL Vulnerability > > > > From the developer mailing list: > > > > Hi, we don't link our odbc driver with openssl libraries. We load them > dynamically. So don't worry, our odbc driver is not affected at all. > Moreover, it supports multiple versions of openssl, up to 3.0.x > > (Thanks to Ivan Daschinskiy.) > > > > On 8 Nov 2022, at 09:52, Entwicklung <entwickl...@giftinfo.uni-mainz.de> > wrote: > > > > Hello, > > I plan to install Apache Ignite version 2.14.0 binary release (latest) on > a windows server. I prefer ODBC-Connection to my application. > > > Problem: > ODBC uses OpenSSL, but Version 3.0.0 to 3.0.6 has critical vulnerability. > Version 3.0.7 has fixed the problems. Is 2.14.0 binary release (especially > ODBC) affected ? If yes, when is a new binary release available with > OpenSSL 3.0.7. > I could not find any information about the OpenSSL version that Ignite > binaries were built from or used, especially ODBC. > > Thank you for your help > > > Regards > Guido Clesius > > >
