Good question. I've asked it myself. I've been planning on doing an upgrade to support OpenSSL 3.X.+ that maintains support for 1.1.X. That said, it's been at least a year and I haven't gotten around to it, and I'm not firmly committed to the idea of maintaining backwards compatibility. I think that if we're going to break backwards compatibility with older versions, the upgrade to 3.X would probably be a good time to do it. From what little I've read on the subject, the move from 1.1.1 to 3.X is a significant change. In short, I would be in favor of dropping legacy OpenSSL support in the next commons crypto release.
Alex On Sun, Oct 29, 2023 at 9:15 AM sebb <seb...@gmail.com> wrote: > There is quite a lot of Crypto code that depends on the check: > > if (dlsym_OpenSSL_version_num() < VERSION_1_1_X) > where > VERSION_1_1_X = 0x10100000; > > Dropping such support would simplify the code. > > Is there any need to continue to support such old versions? > > Sebb > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > >
