大网数据广告活动
服务器运维问答

Updated the openssl version, but the old version still appears as being used

· 52CE 我爱测

I updated to openssl 1.0.2h, but when I hit lsof | grep -i libssl I still get 1.0.1e nginx 19645 nginx mem REG 182,420273 441256 398853 /usr/lib64/libssl.so.1.0.1e I tried restarting nginx, apache and mysql, but the old version s…

问题原文

原帖链接 · Punct Ulica · CC BY-SA 3.0

I updated to openssl 1.0.2h, but when I hit

lsof | grep -i libssl 

I still get 1.0.1e

nginx     19645        nginx  mem       REG         182,420273    441256     398853 /usr/lib64/libssl.so.1.0.1e

I tried restarting nginx, apache and mysql, but the old version still remains although openssl version returns

OpenSSL 1.0.2h  3 May 2016

I followed the tutorial from here.

Also, before I posted this, I followed the answer from here.

Do you know how I can make it use the latest version?

已采纳解答

原帖链接 · MadHatter · CC BY-SA 3.0

You are solving this problem the wrong way. You need to understand Red Hat's patching policy (CentOS following upstream as it does, this is therefore CentOS's patching policy as well).

As long as C6 is supported (ie, until 2020-11-30), and as long as you keep your C6 box fully up-to-patch, you will be running non-vulnerable versions of OpenSSL even though the OpenSSL version number does not change.

Once you start building your own version of OpenSSL, you will find you have to rebuild (or at least relink) lots of major tools, to get them to pick up your handbuilt version, and you will have to do this each time a new version of OpenSSL comes out. It is a slough of despond, it is completely pointless, and it is unprofessional to boot.

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Server Fault
适用范围
以原帖系统、软件版本与发布日期为准(2016-07-13)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 3.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。