Generic question, is there a way to have the openssl package use ciphers that were moved to legacy library after OpenSSL v3.x?
Edit: I know I can use the legacy ciphers on the openssl command line, not sure why it never occurred to me to make them available in a custom opesnssl.cnf, so .. nevermind, the Crystal openssl package will now do what I’d intended.
I seem to have received two replies to the post I’d made regarding OpenSSL and legacy ciphers that appear in my email, but I don’t see them on the actual forum (?)
They were removed as were just spam replies.
With regard to this initial post, I have a specific case use for cast5, and making a custom openssl.cnf worked when I tested at home. However, here at work, I use a Windows computer, and I made an environment variable OPENSSL_CONF to point to a modified openssl.cnf kept in /mingw64/.. I made a --static binary and everything worked fine. However, when I retired that particular environment variable, I get a “cipher not supported” error. I re-establish that env variable, and it works again. I would’ve thought that making a --static binary would’ve written the legacy provider into the program, was I mistaken in that assumption? Also, I’m not a programmer or anything, so I really just don’t know.
openssl.cnf is runtime configuration. It gets evaluated every time your program runs (uses OpenSSL), not at compile time.