On openSUSE 13.2, the warning /lib64/libcrypto.so.1.0.0: no version information available (required by /lib64/libuastack.so) indicates that the OpenSSL development libraries used to link the OPC UA stack do not match the installed OpenSSL runtime libraries. Recompiling the OPC UA library and application alone will not resolve that mismatch.
Interpret the Warning
The application may continue to run despite the warning, as observed in this case. However, successful startup does not prove that every OpenSSL-dependent path is compatible. Treat the message as a library consistency problem and verify the dependency set before deploying the application.
| Evidence | Engineering conclusion |
|---|---|
Warning names /lib64/libcrypto.so.1.0.0
|
The loaded OpenSSL crypto library lacks version information expected by another component. |
Warning names /lib64/libuastack.so
|
The OPC UA stack is the component requesting that version information. |
| Application still operates | The warning is not an immediate startup failure, but compatibility remains unverified. |
Correct the Library Mismatch
Use OpenSSL development libraries that match the OpenSSL runtime libraries installed on the system. The openSUSE installation already provides a working OpenSSL version, so compiling OpenSSL manually is not required by the available evidence.
- Identify the installed OpenSSL runtime package that supplies
/lib64/libcrypto.so.1.0.0. - Confirm that the installed OpenSSL development package matches that runtime package.
- After correcting any package mismatch, rebuild
libuastack.soand then rebuild or relink the application against the matching development libraries.
Verify the Repair
Run the rebuilt application and confirm that the loader no longer reports missing version information for libcrypto.so.1.0.0. Then exercise the application's OPC UA and OpenSSL-dependent functions; application startup alone is insufficient verification.
If the warning remains, verify which physical OpenSSL library the application loads and which development library was selected during the build. The evidence does not provide package names, build flags, or library search paths, so inspect those values in the actual build and runtime environments rather than assuming them.
FAQ
Why does libcrypto.so.1.0.0 report no version information?
The OpenSSL development libraries used when linking libuastack.so do not match the installed OpenSSL runtime libraries.
Must I compile OpenSSL to fix this openSUSE warning?
No. The available evidence says openSUSE supplies a working OpenSSL version; install matching runtime and development libraries, then rebuild the dependent software.
Is the libcrypto version warning safe to ignore if the application runs?
No compatibility conclusion can be drawn from startup alone. Remove the library mismatch and verify the OPC UA and OpenSSL-dependent application functions.
