search

NICMx / FORT-validator

RPKI cache validator
MIT License
51 stars 24 forks source link

Improve installation documentation for RHEL/CentOS and Fedora #27

Closed robert-scheck closed 4 years ago

robert-scheck commented 4 years ago

This documentation update assumes that openssl11-1.1.1c-1.el7 is already in the EPEL 7 stable repository, which will be in about 12 days. Until then it's yum install --enablerepo=epel-testing openssl11-devel obviously.

pcarana commented 4 years ago

Many thanks for this PR @robert-scheck! The process is much simpler than the current.

I took the liberty to commit an update (just a minor detail).

The PR seems fine, we will wait ~10 days until the OpenSSL update is at the EPEL 7 stable repo. Once the update is there, this PR will be merged into master.

We only noticed some warnings at CentOS 7. We're trying to find the cause, but apparently they make no harm since FORT still keeps working. If you know something about this warnings, your comments/guidance on this will be really appreciated:

/opt/rh/devtoolset-8/root/usr/libexec/gcc/x86_64-redhat-linux/8/ld: warning: libssl.so.10, needed by //lib64/libssh2.so.1, may conflict with libssl.so.1.1
/opt/rh/devtoolset-8/root/usr/libexec/gcc/x86_64-redhat-linux/8/ld: warning: libcrypto.so.10, needed by //lib64/libssh2.so.1, may conflict with libcrypto.so.1.1
robert-scheck commented 4 years ago

@pcarana, the warnings are caused because the FORT-validator started requiring libcurl recently (and libcurl requires libssh2). And libssh2 comes from RHEL/CentOS 7 itself and is linked against OpenSSL 1.0.x (until RHEL/CentOS 7 goes EOL in 2024). So this can not be solved for RHEL/CentOS 7 (it also exists with the previous/current steps) except if somebody provides either an alternative libcurl package (that is not linked against libssh2) or an alternative libssh2 package (that is already linked against OpenSSL 1.1.x) - or of course, if the user builds either of the two itself while respecting before mentioned conditions. The current warning should not cause harms from my point of view except if the libcurl usage in FORT-validator really requires OpenSSL 1.1.x (which currently doesn't seem to be the case)…interesting that you start caring about this warning now and not before already (as it's not caused by my documentation improvement) ;-)

pcarana commented 4 years ago

Hmm ok, that makes sense, thanks for your explanation :)

The current warning should not cause harms from my point of view

That's correct, currently there are no issues related to those warnings and FORT validator keeps doing its job as it should.

interesting that you start caring about this warning now and not before already (as it's not caused by my documentation improvement)

Sorry about that, I believe I wasn't very clear asking for you help on this subject. You're right saying that those warnings aren't caused by your docs improvement, they are already present using the current documentation. I was actually looking forward to get your aid on this, because I believe that your experience could help us to find the cause of such warnings (and that's precisely what happened).

robert-scheck commented 4 years ago

I was actually looking forward to get your aid on this, because I believe that your experience could help us to find the cause of such warnings (and that's precisely what happened).

Ah. I'm sorry for not getting this…but should be clarified anyway now :)

robert-scheck commented 4 years ago

The package openssl11-1.1.1c-1.el7 has been pushed to the EPEL stable updates repository about two days ago.

pcarana commented 4 years ago

Great news! This will be merged :+1: