OpenSSL Tracer Installation
The tracer requires installing the
libunwind library which is used to retrieve stack
If you want the trace to contain complete stack traces for calls to the OpenSSL library, the application to be traced should be built with debug symbols. If the application is not built with debug symbols, the tracer will still work, but you will only see the calls to the libraries, and not the stack traces. However, it is not useful to build the OpenSSL libraries in debug mode.
Cryptosense OpenSSL tracer comes in different versions, one for each supported version of OpenSSL. At the time of this writing, OpenSSL 0.9.8, 1.0.x and 1.1.x are supported. Therefore, you will also need to know which version of the OpenSSL libraries your application uses. If you don't know this information, the reference manual has some instructions on how to figure it out.
The Cryptosense OpenSSL tracer is distributed as a zip archive.
You will have a
cs-openssl-tracer-<VERSION>.zip file. When you unzip the package, you
will have several directories, containing the tracers for different versions of OpenSSL,
cs-openssl-tracer-0.0.3 ├── cs-tracer-openssl-0.9.8 │ ├── evp_tracer.so │ └── libssl_tracer.so ├── cs-tracer-openssl-1.0 │ ├── evp_tracer.so │ └── libssl_tracer.so ├── cs-tracer-openssl-1.0-rhel7 │ ├── evp_tracer.so │ └── libssl_tracer.so ├── cs-tracer-openssl-1.1 │ ├── evp_tracer.so │ └── libssl_tracer.so └── README.md
You may move those files to anywhere you want on your system. They do not have to remain