Only include custom OpenSSL ABI checks for OpenSSL 1.1

OpenSSL has a Policy on API compatibility in minor releases saying:

Only API additions are allowed in minor releases.

Minor releases are defined as 3.X.0. A change to 4.X.X would change the libssl.so.3 SONAME to libssl.so.4 so the (possibly) incompatible library would not get loaded in the first place.

This warning message is causing confusion between unrelated issues in the Arch Linux bug tracker.

requested review from @ahf

changed milestone to %Tor: 0.4.9.x-freeze

Can you link to some of these issues? That sounds interesting.

https://gitlab.archlinux.org/archlinux/packaging/packages/tor/-/issues/3#note_161857

@dgoulet Should we consider to relax these rules? These and our ABI/API checks of compression libs has before been a nightmare for downstream projects. Particularly zstd was causing trouble because we want their private API.

I think this is fine.

@dgoulet Does "this is fine" mean "the patch is fine, let's merge it"? Or "the status quo is fine, let's reject the MR"?

Arch decided: "As per above the crashes are fixed. But upstream haven't yet applied the MR. Oh well, not really our problem..."

@ahf We get this in?

@dgoulet I think we should get it in, yea. I won't have time today tho :-/

approved this merge request

That is fine, its looks good. Merging into 049.

merged

mentioned in commit 9a1e633b

Thanks!