[MDEV-27542] S3 binaries still link with OpenSSL 1.x or with both Created: 2022-01-18 Updated: 2022-01-19 Resolved: 2022-01-19 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Compiling, SSL, Storage Engine - S3 |
| Affects Version/s: | N/A |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Minor |
| Reporter: | Elena Stepanova | Assignee: | Sergei Golubchik |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||
| Description |
|
S3-related binaries link with the old openssl even when cmake points at openssl-3 and the server builds with it. I'm not sure what will happen if the system doesn't have openssl-1 at all – whether they'll resort to openssl-3 or won't build at all. Maybe it has something to do with them also linking with libk5crypto.so or libhcrypto.so, I can't figure what these are and how they relate to openssl-X version-wise or otherwise.
Also some link only with libk5crypto.so:
|
| Comments |
| Comment by Vladislav Vaintroub [ 2022-01-19 ] |
|
auth_gssapi links with whatever krb5-config says it should link with (see plugin/auth_gssapi/cmake/FindGSSAPI.cmake) In case of S3, a wild guess is that dependencies come by the way of CURL, linked together to dependency libmarias3 |
| Comment by Sergei Golubchik [ 2022-01-19 ] |
|
Right. If a plugin is linked with some library that is in turn linked with an older OpenSSL — there's nothing we can fix here. As far as curl is concerned, it doesn't need OpenSSL as such, it can be built with GnuTLS, for example. |