ripem160 issues on Ubuntu 22

Anyone else dealing with this problem and figured out a fix? I've gone through all the suggestions online and still can't get it to work on Ubuntu 22. It should function if I enable it manually, but that’s not happening for me: https://stackoverflow.com/questions/69922525/python-3-9-8-hashlib-and-ripemd160/72509045#72509045 Funny part is, it works just fine on Ubuntu 18... thanks!

What OpenSSL version?

hey achow101... OpenSSL 3.0.2 15 Mar 2022 (Library: OpenSSL 3.0.2 15 Mar 2022) I edited manually the openssl.cnf as in the tutorial: Make sure that the config file contains following lines: openssl_conf = openssl_init [openssl_init] providers = provider_sect [provider_sect] default = default_sect legacy = legacy_sect [default_sect] activate = 1 [legacy_sect] activate = 1 But still not working..

Where did you put the openssl.cnf file?

According to that guide I read I edited this one: /usr/lib/ssl/openssl.cnf but I notice there are others: /etc/ssl/openssl.cnf /snap/core20/1587/etc/ssl/openssl.cnf /snap/core20/1587/usr/lib/ssl/openssl.cnf /snap/core20/2318/etc/ssl/openssl.cnf /snap/core20/2318/usr/lib/ssl/openssl.cnf /usr/lib/shim/mok/openssl.cnf /usr/lib/ssl/openssl.cnf /usr/share/doc/nodejs/openssl.cnf.gz /usr/share/doc/openvpn/examples/sample-keys/openssl.cnf I am not ot sure which one should be?

What is the result of

I got this: OPENSSLDIR: "/usr/lib/ssl"

Does openssl list -providers mention "OpenSSL Legacy Provider" somewhere? If not, then it appears that your configuration is not taking effect. Also you may have to restart system services or reboot the computer to apply the new openssl settings to each program.

yes it does have legacy..but still not working. This is very annoying, since I got Ubuntu18 and it does works well there... mahuro@WorkStation:~/Desktop$ openssl list -providers Providers:   default     name: OpenSSL Default Provider     version: 3.0.2     status: active   legacy     name: OpenSSL Legacy Provider     version: 3.0.2     status: active

Which programs are you trying to use that require the legacy provider? It is possible that they might be linked to a different version of OpenSSL. You can check on Linux which libraries a program is linked to by running ldd $(which <program>). For example, if you are trying to check the libraries that Python uses: Should print something like this: See if they are using custom versions of OpenSSL. You should see a library called libssl or something like that. A custom installation of OpenSSL will have its own configuration files.