多openssl版本共存，如何再装一个openssl低版本

openssl

传输层安全性/安全套接层及其加密库

项目地址：https://gitcode.com/gh_mirrors/ope/openssl

免费下载资源

天马行空skywalk

2206人浏览 · 2024-01-29 22:58:19

天马行空skywalk · 2024-01-29 22:58:19 发布

在编译安装TrinityCore的时候，碰到报错：

报错：
CMake Error at cmake/macros/FindOpenSSL.cmake:579 (message):
TrinityCore needs OpenSSL version 1.0 but found too new version .
TrinityCore needs OpenSSL 1.0.x or 1.1.x to work properly. If you still
have problems please install OpenSSL 1.0.x if you still have problems
search on forum for TCE00022
Call Stack (most recent call first):
dep/openssl/CMakeLists.txt:16 (find_package)

由于不能降低openssl版本，以免影响当前的应用，所以只好再装一个1.0.x的版本。

下载：

OpenSSL官方下载 - 码客

tar -xzvf 解压后，

进入openssl目录进行编译。

make ，报错：
making all in crypto...
make[1]: Entering directory '/home/wow/work/openssl-1.0.2p/crypto'
make[1]: *** No rule to make target '../include/openssl/bio.h', needed by 'cryptlib.o'. Stop.

原来需要先config再make
./config

make

现在就编译好了低版本的opensll，在编译安装TrinityCore的时候，加上参数：

-DOPENSSL_LIBRARIES=path to OpenSSL library
-DOPENSSL_INCLUDE_DIR=path to OpenSSL includes

问题解决！

GitHub 加速计划 / ope / openssl

下载

传输层安全性/安全套接层及其加密库

最近提交(Master分支：6 个月前 )

ddd99d52 We use the same extension-parsing function on server and client for convenience, but while the server might worry about tracking what was previously received and not overwriting it, on the client receiving a request for post-handshake authentication, we always want to use the values from the current extension (and should always have a new session object that we are free to mutate). It is somewhat unclear whether the server also needs the check for a resumed connection; it appears to have been added back in 2015 in commit 062178678f5374b09f00d70796f6e692e8775aca as part of a broad pass to handle extensions on resumption, but without specific documentation of each extension's handling. Fixes: #10370 Reviewed-by: Dmitry Belyavskiy <beldmit@gmail.com> Reviewed-by: Tomas Mraz <tomas@openssl.org> (Merged from https://github.com/openssl/openssl/pull/24651) 4 小时前

dad4704a Make building with --strict-warnings the default for most builds. Move this option to immediately after the ./config command so its presence is clearer. Reviewed-by: Tom Cosgrove <tom.cosgrove@arm.com> Reviewed-by: Tomas Mraz <tomas@openssl.org> (Merged from https://github.com/openssl/openssl/pull/27204) 4 小时前