View Single Post
Old 09-02-2023, 01:52 PM   #334
Leseratte_10
Groupie
Leseratte_10 ought to be getting tired of karma fortunes by now.Leseratte_10 ought to be getting tired of karma fortunes by now.Leseratte_10 ought to be getting tired of karma fortunes by now.Leseratte_10 ought to be getting tired of karma fortunes by now.Leseratte_10 ought to be getting tired of karma fortunes by now.Leseratte_10 ought to be getting tired of karma fortunes by now.Leseratte_10 ought to be getting tired of karma fortunes by now.Leseratte_10 ought to be getting tired of karma fortunes by now.Leseratte_10 ought to be getting tired of karma fortunes by now.Leseratte_10 ought to be getting tired of karma fortunes by now.Leseratte_10 ought to be getting tired of karma fortunes by now.
 
Posts: 183
Karma: 3587000
Join Date: Sep 2021
Device: PB Era, PB InkPad 3 Pro
This looks like it's a bug in oscrypto, the library my plugin uses for cryptography stuff.

https://github.com/wbond/oscrypto/issues/78

I can take a look in a couple days and see if I can find a workaround.

Can you post the output of "openssl version" on the command line?

EDIT: Confirmed, bug in oscrypto.
As soon as the system is updated to openssl 3.0.10 or higher the python module fails because they have a buggy regex that only accepts single-digit version numbers. There's not much you can do in the meantime, sadly, other than maybe trying to downgrade openssl again, but that may break your system or other applications.

So this is the same situation as back then when openssl 3 came out, sooner or later everyone will run into this bug.

I'll try to find a workaround asap; and I'll try to find some time soon-ish to finally finish and release 0.1.0 with all the fixes since then.

Last edited by Leseratte_10; 09-02-2023 at 03:10 PM.
Leseratte_10 is offline   Reply With Quote