>libcrypto.a and libcrypto.so are files which are built by
linux-compiler?
but somewhere has to be the source code for them ?
The files in the crypto directory are compiled to build the libraries.
I think you will find some intro material on building C software useful. This
is pr
This is tricky to dig for the source code.
I guess I would need the source code for libcrypto.a and for
libcrypto.so,
but so they are not part of openssl-package ...
libcrypto.a and libcrypto.so are files which are built by
linux-compiler?
but somewhere has to be the source code for them ?
A
On Wed, Jul 18, 2018 at 03:24:31PM -0500, Ryan Beethe wrote:
> For a safe client application, should you explicitly set the cipher list
> explicitly, rather than trust the default cipher list that comes from
> the package manager's libssl?
I would say that the answer to that depends on another que
On 19/07/18 07:08, pratyush parimal wrote:
> Hi all,
>
> Are people familiar with how to get symbols versioned with versions
> like "OPENSSL_1.0.x" in the libcrypto.so after compiling it
> yourselves?
OpenSSL as sourced from the OpenSSL project does not support this in 1.0.x.
> Problem is, on
