Re: Does kyua based testing need some hazmat/bindings/_openssl.abi3.so related updating?: Undefined symbol "ERR_GET_FUNC"

2023-07-12 Thread Enji Cooper 

> On Jul 10, 2023, at 3:27 PM, Mark Millard  wrote:
> 
> On Jul 10, 2023, at 15:03, Mark Millard  > wrote:
> 
>> On Jul 10, 2023, at 11:42, The Doctor  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:
 
 # kyua report --verbose 
 --results-file=usr_obj_DESTDIRs_main-CA7-chroot_usr_tests.20230710-064632-752785
  2>&1 | grep "Undefined symbol" | sort -u
 +ImportError: 
 /usr/obj/DESTDIRs/main-CA7-chroot/usr/local/lib/python3.9/site-packages/cryptography/hazmat/bindings/_openssl.abi3.so:
  Undefined symbol "ERR_GET_FUNC"
 ImportError: 
 /usr/local/lib/python3.9/site-packages/cryptography/hazmat/bindings/_openssl.abi3.so:
  Undefined symbol "ERR_GET_FUNC"
 ImportError: 
 /usr/obj/DESTDIRs/main-CA7-chroot/usr/local/lib/python3.9/site-packages/cryptography/hazmat/bindings/_openssl.abi3.so:
  Undefined symbol "ERR_GET_FUNC"
 
 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.
 
>>> 
>>> No! The problem is that Python is calling an openssl 1.X function
>>> which is dropped in Opensss 3.X
>>> 
>>> Python nedds to fix that issue.
>> 
>> Well:
>> 
>> # strings 
>> /usr/obj/DESTDIRs/main-CA7-chroot/usr/local/lib/python3.9/site-packages/cryptography/hazmat/bindings/_openssl.abi3.so
>>  | grep -i "3\.[0-9]*\.[0-9]"
>> OpenSSL 3.0.9 30 May 2023
>> 3.4.8
>> 
>> From 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 "?".
>> 
> 
> 35.0.0 of cryptography dates back to 2021-09-29.
> Current for cryptography is 41.0.1 (2023-06-01).
> It claims: "It supports Python 3.7+ and PyPy3
> 7.3.10+."
> 
> security/py-cryptography is at 3.4.8 (2021-08-24)
> for py39-cryptography and is, in-part, a FreeBSD
> ports issue as far as I can tell.
> 
> Looking, it seems it is at 3.4.8 for all @${PY_FLAVOR}
> instances. So trying python310 or python311 might
> well do no good for openssl 3.0 compatibility if they
> use security/py-cryptography .
> 
> (Note: I build my own ports via poudriere-devel .)

py-cryptography in ports doesn’t support OpenSSL 3. Please see this issue for 
more details: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254853 
 .
Thanks,
-Enji


signature.asc
Description: Message signed with OpenPGP

Re: Does kyua based testing need some hazmat/bindings/_openssl.abi3.so related updating?: Undefined symbol "ERR_GET_FUNC"

2023-07-10 Thread Mark Millard 
On Jul 10, 2023, at 15:03, Mark Millard  wrote:

> On Jul 10, 2023, at 11:42, The Doctor  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:
>>> 
>>> # kyua report --verbose 
>>> --results-file=usr_obj_DESTDIRs_main-CA7-chroot_usr_tests.20230710-064632-752785
>>>  2>&1 | grep "Undefined symbol" | sort -u
>>> +ImportError: 
>>> /usr/obj/DESTDIRs/main-CA7-chroot/usr/local/lib/python3.9/site-packages/cryptography/hazmat/bindings/_openssl.abi3.so:
>>>  Undefined symbol "ERR_GET_FUNC"
>>> ImportError: 
>>> /usr/local/lib/python3.9/site-packages/cryptography/hazmat/bindings/_openssl.abi3.so:
>>>  Undefined symbol "ERR_GET_FUNC"
>>> ImportError: 
>>> /usr/obj/DESTDIRs/main-CA7-chroot/usr/local/lib/python3.9/site-packages/cryptography/hazmat/bindings/_openssl.abi3.so:
>>>  Undefined symbol "ERR_GET_FUNC"
>>> 
>>> 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.
>>> 
>> 
>> No! The problem is that Python is calling an openssl 1.X function
>> which is dropped in Opensss 3.X
>> 
>> Python nedds to fix that issue.
> 
> Well:
> 
> # strings 
> /usr/obj/DESTDIRs/main-CA7-chroot/usr/local/lib/python3.9/site-packages/cryptography/hazmat/bindings/_openssl.abi3.so
>  | grep -i "3\.[0-9]*\.[0-9]"
> OpenSSL 3.0.9 30 May 2023
> 3.4.8
> 
> From 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 "?".
> 

35.0.0 of cryptography dates back to 2021-09-29.
Current for cryptography is 41.0.1 (2023-06-01).
It claims: "It supports Python 3.7+ and PyPy3
7.3.10+."

security/py-cryptography is at 3.4.8 (2021-08-24)
for py39-cryptography and is, in-part, a FreeBSD
ports issue as far as I can tell.

Looking, it seems it is at 3.4.8 for all @${PY_FLAVOR}
instances. So trying python310 or python311 might
well do no good for openssl 3.0 compatibility if they
use security/py-cryptography .

(Note: I build my own ports via poudriere-devel .)

===
Mark Millard
marklmi at yahoo.com

Re: Does kyua based testing need some hazmat/bindings/_openssl.abi3.so related updating?: Undefined symbol "ERR_GET_FUNC"

2023-07-10 Thread Mark Millard 
On Jul 10, 2023, at 11:42, The Doctor  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:
>> 
>> # kyua report --verbose 
>> --results-file=usr_obj_DESTDIRs_main-CA7-chroot_usr_tests.20230710-064632-752785
>>  2>&1 | grep "Undefined symbol" | sort -u
>> +ImportError: 
>> /usr/obj/DESTDIRs/main-CA7-chroot/usr/local/lib/python3.9/site-packages/cryptography/hazmat/bindings/_openssl.abi3.so:
>>  Undefined symbol "ERR_GET_FUNC"
>> ImportError: 
>> /usr/local/lib/python3.9/site-packages/cryptography/hazmat/bindings/_openssl.abi3.so:
>>  Undefined symbol "ERR_GET_FUNC"
>> ImportError: 
>> /usr/obj/DESTDIRs/main-CA7-chroot/usr/local/lib/python3.9/site-packages/cryptography/hazmat/bindings/_openssl.abi3.so:
>>  Undefined symbol "ERR_GET_FUNC"
>> 
>> 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.
>> 
> 
> No! The problem is that Python is calling an openssl 1.X function
> which is dropped in Opensss 3.X
> 
> Python nedds to fix that issue.

Well:

# strings 
/usr/obj/DESTDIRs/main-CA7-chroot/usr/local/lib/python3.9/site-packages/cryptography/hazmat/bindings/_openssl.abi3.so
 | grep -i "3\.[0-9]*\.[0-9]"
OpenSSL 3.0.9 30 May 2023
3.4.8

From 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 "?".


===
Mark Millard
marklmi at yahoo.com

Re: Does kyua based testing need some hazmat/bindings/_openssl.abi3.so related updating?: Undefined symbol "ERR_GET_FUNC"

2023-07-10 Thread The Doctor 
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:
> 
> # kyua report --verbose 
> --results-file=usr_obj_DESTDIRs_main-CA7-chroot_usr_tests.20230710-064632-752785
>  2>&1 | grep "Undefined symbol" | sort -u
> +ImportError: 
> /usr/obj/DESTDIRs/main-CA7-chroot/usr/local/lib/python3.9/site-packages/cryptography/hazmat/bindings/_openssl.abi3.so:
>  Undefined symbol "ERR_GET_FUNC"
> ImportError: 
> /usr/local/lib/python3.9/site-packages/cryptography/hazmat/bindings/_openssl.abi3.so:
>  Undefined symbol "ERR_GET_FUNC"
> ImportError: 
> /usr/obj/DESTDIRs/main-CA7-chroot/usr/local/lib/python3.9/site-packages/cryptography/hazmat/bindings/_openssl.abi3.so:
>  Undefined symbol "ERR_GET_FUNC"
> 
> 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.
>

No! The problem is that Python is calling an openssl 1.X function
which is dropped in Opensss 3.X

Python nedds to fix that issue.

> ===
> Mark Millard
> marklmi at yahoo.com
> 
> 

-- 
Member - Liberal International This is doc...@nk.ca Ici doc...@nk.ca
Yahweh, King & country!Never Satan President Republic!Beware AntiChrist rising!
Look at Psalms 14 and 53 on Atheism https://www.empire.kred/ROOTNK?t=94a1f39b 
"We should do good unless it inconveniences us," is not righteous thinking. 
-unknown Beware https://mindspring.com

Re: Does kyua based testing need some hazmat/bindings/_openssl.abi3.so related updating?: Undefined symbol "ERR_GET_FUNC"

2023-07-10 Thread Mark Millard 
On Jul 10, 2023, at 10:55, Mark Millard  wrote:

> On Jul 10, 2023, at 09:45, Mike Karels  wrote:
> 
>> On 10 Jul 2023, at 10:56, Mark Millard wrote:
>> 
>>> The subject line's question was prompted by
>>> . . ./hazmat/bindings/_openssl.abi3.so related notices
>>> in a kyua report:
>>> 
>>> # kyua report --verbose 
>>> --results-file=usr_obj_DESTDIRs_main-CA7-chroot_usr_tests.20230710-064632-752785
>>>  2>&1 | grep "Undefined symbol" | sort -u
>>> +ImportError: 
>>> /usr/obj/DESTDIRs/main-CA7-chroot/usr/local/lib/python3.9/site-packages/cryptography/hazmat/bindings/_openssl.abi3.so:
>>>  Undefined symbol "ERR_GET_FUNC"
>>> ImportError: 
>>> /usr/local/lib/python3.9/site-packages/cryptography/hazmat/bindings/_openssl.abi3.so:
>>>  Undefined symbol "ERR_GET_FUNC"
>>> ImportError: 
>>> /usr/obj/DESTDIRs/main-CA7-chroot/usr/local/lib/python3.9/site-packages/cryptography/hazmat/bindings/_openssl.abi3.so:
>>>  Undefined symbol "ERR_GET_FUNC"
>>> 
>>> 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.
>> 
>> I haven't seen this.  My v7 environments (chroot and /usr/lib32) have
>> only libssl.so.3, not .111, so they must be using OpenSSL 3.0.
> 
> But is the phython3 use by kyua of aarch64 code? armv7 code?
> 
> # file /usr/obj/DESTDIRs/main-CA7-chroot/usr/bin/kyua
> /usr/obj/DESTDIRs/main-CA7-chroot/usr/bin/kyua: ELF 32-bit LSB executable, 
> ARM, EABI5 version 1 (FreeBSD), dynamically linked, interpreter 
> /libexec/ld-elf.so.1, FreeBSD-style, for FreeBSD 14.0 (1400092), not stripped
> 
> So: armv7 for my lib32 testing activity.
> 
>> Which version of kyua is this running (32 or 64 bit)?
> 
> armv7 (so: 32-bit). This is using my way of causing more
> code to be armv7 instead of aarch64 processes for lib32
> testing than I expect your testing technique ends up
> with.
> 
> # file /usr/obj/DESTDIRs/main-CA7-chroot/usr/bin/kyua
> /usr/obj/DESTDIRs/main-CA7-chroot/usr/bin/kyua: ELF 32-bit LSB executable, 
> ARM, EABI5 version 1 (FreeBSD), dynamically linked, interpreter 
> /libexec/ld-elf.so.1, FreeBSD-style, for FreeBSD 14.0 (1400092), not stripped
> 
> For reference:
> 
> /usr/obj/DESTDIRs/main-CA7-chroot/usr/lib/libssl.so
> /usr/obj/DESTDIRs/main-CA7-chroot/usr/lib/libssl.so.30
> 
> As for the aarch4 boot environment:
> 
> /usr/lib/libssl.so
> /usr/lib/libssl.so.30

I forgot to list:

/usr/lib32/libssl.so.30
/usr/lib32/libssl.so

Sorry for the confusion.

> There are no *.111* files on the system other than some
> old log files or other archiving of old things in 2
> separate old-stuff directory trees that are not in
> use.


===
Mark Millard
marklmi at yahoo.com

Re: Does kyua based testing need some hazmat/bindings/_openssl.abi3.so related updating?: Undefined symbol "ERR_GET_FUNC"

2023-07-10 Thread Mark Millard 
On Jul 10, 2023, at 09:45, Mike Karels  wrote:

> On 10 Jul 2023, at 10:56, Mark Millard wrote:
> 
>> The subject line's question was prompted by
>> . . ./hazmat/bindings/_openssl.abi3.so related notices
>> in a kyua report:
>> 
>> # kyua report --verbose 
>> --results-file=usr_obj_DESTDIRs_main-CA7-chroot_usr_tests.20230710-064632-752785
>>  2>&1 | grep "Undefined symbol" | sort -u
>> +ImportError: 
>> /usr/obj/DESTDIRs/main-CA7-chroot/usr/local/lib/python3.9/site-packages/cryptography/hazmat/bindings/_openssl.abi3.so:
>>  Undefined symbol "ERR_GET_FUNC"
>> ImportError: 
>> /usr/local/lib/python3.9/site-packages/cryptography/hazmat/bindings/_openssl.abi3.so:
>>  Undefined symbol "ERR_GET_FUNC"
>> ImportError: 
>> /usr/obj/DESTDIRs/main-CA7-chroot/usr/local/lib/python3.9/site-packages/cryptography/hazmat/bindings/_openssl.abi3.so:
>>  Undefined symbol "ERR_GET_FUNC"
>> 
>> 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.
> 
> I haven't seen this.  My v7 environments (chroot and /usr/lib32) have
> only libssl.so.3, not .111, so they must be using OpenSSL 3.0.

But is the phython3 use by kyua of aarch64 code? armv7 code?

# file /usr/obj/DESTDIRs/main-CA7-chroot/usr/bin/kyua
/usr/obj/DESTDIRs/main-CA7-chroot/usr/bin/kyua: ELF 32-bit LSB executable, ARM, 
EABI5 version 1 (FreeBSD), dynamically linked, interpreter 
/libexec/ld-elf.so.1, FreeBSD-style, for FreeBSD 14.0 (1400092), not stripped

So: armv7 for my lib32 testing activity.

> Which version of kyua is this running (32 or 64 bit)?

armv7 (so: 32-bit). This is using my way of causing more
code to be armv7 instead of aarch64 processes for lib32
testing than I expect your testing technique ends up
with.

# file /usr/obj/DESTDIRs/main-CA7-chroot/usr/bin/kyua
/usr/obj/DESTDIRs/main-CA7-chroot/usr/bin/kyua: ELF 32-bit LSB executable, ARM, 
EABI5 version 1 (FreeBSD), dynamically linked, interpreter 
/libexec/ld-elf.so.1, FreeBSD-style, for FreeBSD 14.0 (1400092), not stripped

For reference:

/usr/obj/DESTDIRs/main-CA7-chroot/usr/lib/libssl.so
/usr/obj/DESTDIRs/main-CA7-chroot/usr/lib/libssl.so.30

As for the aarch4 boot environment:

/usr/lib/libssl.so
/usr/lib/libssl.so.30

There are no *.111* files on the system other than some
old log files or other archiving of old things in 2
separate old-stuff directory trees that are not in
use.

===
Mark Millard
marklmi at yahoo.com

Re: Does kyua based testing need some hazmat/bindings/_openssl.abi3.so related updating?: Undefined symbol "ERR_GET_FUNC"

2023-07-10 Thread Mike Karels 
On 10 Jul 2023, at 10:56, Mark Millard wrote:

> The subject line's question was prompted by
> . . ./hazmat/bindings/_openssl.abi3.so related notices
> in a kyua report:
>
> # kyua report --verbose 
> --results-file=usr_obj_DESTDIRs_main-CA7-chroot_usr_tests.20230710-064632-752785
>  2>&1 | grep "Undefined symbol" | sort -u
> +ImportError: 
> /usr/obj/DESTDIRs/main-CA7-chroot/usr/local/lib/python3.9/site-packages/cryptography/hazmat/bindings/_openssl.abi3.so:
>  Undefined symbol "ERR_GET_FUNC"
> ImportError: 
> /usr/local/lib/python3.9/site-packages/cryptography/hazmat/bindings/_openssl.abi3.so:
>  Undefined symbol "ERR_GET_FUNC"
> ImportError: 
> /usr/obj/DESTDIRs/main-CA7-chroot/usr/local/lib/python3.9/site-packages/cryptography/hazmat/bindings/_openssl.abi3.so:
>  Undefined symbol "ERR_GET_FUNC"
>
> 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.

I haven't seen this.  My v7 environments (chroot and /usr/lib32) have
only libssl.so.3, not .111, so they must be using OpenSSL 3.0.

Which version of kyua is this running (32 or 64 bit)?

Mike

> ===
> Mark Millard
> marklmi at yahoo.com

Does kyua based testing need some hazmat/bindings/_openssl.abi3.so related updating?: Undefined symbol "ERR_GET_FUNC"

2023-07-10 Thread Mark Millard 
The subject line's question was prompted by
. . ./hazmat/bindings/_openssl.abi3.so related notices
in a kyua report:

# kyua report --verbose 
--results-file=usr_obj_DESTDIRs_main-CA7-chroot_usr_tests.20230710-064632-752785
 2>&1 | grep "Undefined symbol" | sort -u
+ImportError: 
/usr/obj/DESTDIRs/main-CA7-chroot/usr/local/lib/python3.9/site-packages/cryptography/hazmat/bindings/_openssl.abi3.so:
 Undefined symbol "ERR_GET_FUNC"
ImportError: 
/usr/local/lib/python3.9/site-packages/cryptography/hazmat/bindings/_openssl.abi3.so:
 Undefined symbol "ERR_GET_FUNC"
ImportError: 
/usr/obj/DESTDIRs/main-CA7-chroot/usr/local/lib/python3.9/site-packages/cryptography/hazmat/bindings/_openssl.abi3.so:
 Undefined symbol "ERR_GET_FUNC"

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.

===
Mark Millard
marklmi at yahoo.com