Date: Mon, 10 Jul 2023 15:03:58 -0700 From: Mark Millard <marklmi@yahoo.com> To: The Doctor <doctor@doctor.nl2k.ab.ca> Cc: Current FreeBSD <freebsd-current@freebsd.org>, Mike Karels <mike@karels.net> Subject: Re: Does kyua based testing need some hazmat/bindings/_openssl.abi3.so related updating?: Undefined symbol "ERR_GET_FUNC" Message-ID: <603B7CEE-F3E3-43C4-B031-9C8A1027CA7E@yahoo.com> In-Reply-To: <ZKxRC54P4jAdjiH7@doctor.nl2k.ab.ca> References: <1E426C5E-B363-4C76-A952-48EF404F6557.ref@yahoo.com> <1E426C5E-B363-4C76-A952-48EF404F6557@yahoo.com> <ZKxRC54P4jAdjiH7@doctor.nl2k.ab.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jul 10, 2023, at 11:42, The Doctor <doctor@doctor.nl2k.ab.ca> wrote: > On Mon, Jul 10, 2023 at 08:56:22AM -0700, Mark Millard wrote: >> The subject line's question was prompted by >> . . ./hazmat/bindings/_openssl.abi3.so related notices >> in a kyua report: >>=20 >> # kyua report --verbose = --results-file=3Dusr_obj_DESTDIRs_main-CA7-chroot_usr_tests.20230710-06463= 2-752785 2>&1 | grep "Undefined symbol" | sort -u >> +ImportError: = /usr/obj/DESTDIRs/main-CA7-chroot/usr/local/lib/python3.9/site-packages/cr= yptography/hazmat/bindings/_openssl.abi3.so: Undefined symbol = "ERR_GET_FUNC" >> ImportError: = /usr/local/lib/python3.9/site-packages/cryptography/hazmat/bindings/_opens= sl.abi3.so: Undefined symbol "ERR_GET_FUNC" >> ImportError: = /usr/obj/DESTDIRs/main-CA7-chroot/usr/local/lib/python3.9/site-packages/cr= yptography/hazmat/bindings/_openssl.abi3.so: Undefined symbol = "ERR_GET_FUNC" >>=20 >> It is possible that this is related to some oddities of my >> context for this. But I figured I'd ask the general question >> anyway. >>=20 >=20 > No! The problem is that Python is calling an openssl 1.X function > which is dropped in Opensss 3.X >=20 > Python nedds to fix that issue. Well: # strings = /usr/obj/DESTDIRs/main-CA7-chroot/usr/local/lib/python3.9/site-packages/cr= yptography/hazmat/bindings/_openssl.abi3.so | grep -i "3\.[0-9]*\.[0-9]" OpenSSL 3.0.9 30 May 2023 3.4.8 =46rom what I read, 3.4.8 is too old and is known to have this issue and = this was fixed in a later version. I see references to "cryptography" needing = to be "at least 35.0.0 for OpenSSL 3.0 support" instead of "3.4.8" as one = place put it. I've no clue of the details for python3.9 vs. python3.10 or python3.11 = for containing a sufficiently modern "cryptography" already in FreeBSD ports (vs. not). But this may be more of a port-update issue than an up-stream python issue -- or possibly just a "use python 3.? or later" issue for some value for "?". =3D=3D=3D Mark Millard marklmi at yahoo.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?603B7CEE-F3E3-43C4-B031-9C8A1027CA7E>