Please convert to use the system's crypto policy for SSL and TLS: https://fedoraproject.org/wiki/Packaging:CryptoPolicies If this program is compiled against gnutls, change the default priority string to be "@SYSTEM" or to use gnutls_set_default_priority(). If this program is compiled against openssl, and there is no default cipher list specified, you don't need to modify it. Otherwise replace the default cipher list with "PROFILE=SYSTEM". In both cases please verify that the application uses the system's crypto policies. If the package is already using the system-wide crypto policies, or it does not use SSL or TLS, no action is required, the bug can simply be closed.
rear-1.17.0-1.el5 has been submitted as an update for Fedora EPEL 5. https://admin.fedoraproject.org/updates/rear-1.17.0-1.el5
rear-1.17.0-1.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/rear-1.17.0-1.el6
rear-1.17.0-1.el7 has been submitted as an update for Fedora EPEL 7. https://admin.fedoraproject.org/updates/rear-1.17.0-1.el7
I have not checked the actual releases in EPEL, but note that this change for fedora crypto policies, currently, only works in Fedora 21+. Not in RHEL or any other EL.
I would not worry too much about it. I just added "COPY_AS_IS=( ${COPY_AS_IS[@]} /etc/crypto-policies )" to our frame-work build, which means if /etc/crypto-policies directory is present on the system (whatever distro we running it on) it will be copied to the ram disk of our rescue image. see https://github.com/rear/rear/commit/7ec5eba19c270fee0401422b02462a44f3489722 It is completely harmless, but effective.
rear-1.17.0-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/rear-1.17.0-1.fc20
rear-1.17.0-1.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/rear-1.17.0-1.fc21
rear-1.17.0-1.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/rear-1.17.0-1.fc22
Package rear-1.17.0-1.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing rear-1.17.0-1.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-3860/rear-1.17.0-1.fc20 then log in and leave karma (feedback).
rear-1.17.0-1.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.
rear-1.17.0-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
rear-1.17.0-1.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.
rear-1.17.0-1.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report.
rear-1.17.0-1.el5 has been pushed to the Fedora EPEL 5 stable repository. If problems still persist, please make note of it in this bug report.
rear-1.17.0-1.el7 has been pushed to the Fedora EPEL 7 stable repository. If problems still persist, please make note of it in this bug report.