First, I tried downloading the source tarball openssl-1.0.1s.tar.gz from openssl.org and doing a ./config && make install, and although it seems to have completed the process successfully, I don't know where the compiled code went or if it got installed at all, because I still have a very old version of openssl linked in /usr/bin/, sothat didn't seem to work.
[root@E345 openssl]# openssl version
OpenSSL 1.0.1e-fips 11 Feb 2013
Then, I tried downloading the rpm package and installing with rpm -Uvh and it seemed to install correctly, but with a ton of warnings, and the same exact result as above,
[root@E345 openssl]# rpm -Uvh openssl-1.0.1e-42.el7.9.src.rpm
Updating / installing...
1:openssl-1:1.0.1e-42.el7.9 ################################# [100%]
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
There are about 30 or 40 of those same two warnings.
Again, after installing the rpm, the same output is given:
[root@E345 openssl]# openssl version
OpenSSL 1.0.1e-fips 11 Feb 2013
What am I doing wrong / misunderstanding?
Edit: accidentally pasted the wrong OpenSSL version from another machine
Best Answer
For what it is worth, it generally is a bad practice to compile custom packages on enterprise-level distribution. Most of the time, you should stick with the default distro packages, or only use trusted repositories.
The problem with compiling custom packages, and to directly use RPMs, is that each update is much more labor intensive and error prone than a simple
yum update