| 1 |
.. _linker-warnings: |
| 2 |
|
| 3 |
.. _openssl-versions: |
| 4 |
|
| 5 |
OpenSSL Version Mismatches |
| 6 |
-------------------------- |
| 7 |
|
| 8 |
Your system may have multiple versions of OpenSSL on it. it is possible that |
| 9 |
some libraries which Cyrus can use might be linked against different versions of |
| 10 |
the OpenSSL libraries, or that those may be different from the version which |
| 11 |
Cyrus itself will use. |
| 12 |
|
| 13 |
Major updates of OpenSSL are not always compatible with each other at the API |
| 14 |
level. OpenSSL is used by many libraries and system components and not all of |
| 15 |
those become compatible with the new version at the same time. Because of this |
| 16 |
some Linux distributions choose to ship multiple OpenSSL versions and allow |
| 17 |
components to use whichever version is appropriate. |
| 18 |
|
| 19 |
If two different versions of the OpenSSL libraries linked into one program, it |
| 20 |
results in program instability. To check if this is happening, look for warnings |
| 21 |
from the linker like the following: |
| 22 |
|
| 23 |
.. code-block:: bash |
| 24 |
|
| 25 |
/usr/bin/ld: warning: libssl.so.10, needed by /usr/lib/gcc/x86_64-redhat-linux/7/../../../../lib64/libclamav.so, may conflict with libssl.so.1.1 |
| 26 |
/usr/bin/ld: warning: libcrypto.so.10, needed by /usr/lib/gcc/x86_64-redhat-linux/7/../../../../lib64/libclamav.so, may conflict with libcrypto.so.1.1 |
| 27 |
|
| 28 |
In this case, ClamAV is still linked against OpenSSL 1.0, while Cyrus is |
| 29 |
building with OpenSSL 1.1. |