Description of problem: In f20 I'm getting Unable to retrieve https://gcc.gnu.org: SSL Error while in f17 it is ok, so is firefox or wget on f20. Version-Release number of selected component (if applicable): elinks-0.12-0.37.pre6.fc20.x86_64 How reproducible: links https://gcc.gnu.org I've manually commented out #%patch14 -p1 line and after elinks rebuild it works. As it works with firefox/wget and also https://www.ssllabs.com/ssltest/analyze.html?d=gcc.gnu.org doesn't complain on it, I'd expect there is a problem with the #881411 patch rather than on gcc.gnu.org side.
The server seems to depend on a TLS extension that is not available with ELinks: $ curl -v --sslv3 https://gcc.gnu.org * Rebuilt URL to: https://gcc.gnu.org/ * Adding handle: conn: 0x18cf860 * Adding handle: send: 0 * Adding handle: recv: 0 * Curl_addHandleToPipeline: length: 1 * - Conn 0 (0x18cf860) send_pipe: 1, recv_pipe: 0 * About to connect() to gcc.gnu.org port 443 (#0) * Trying 209.132.180.131... * Connected to gcc.gnu.org (209.132.180.131) port 443 (#0) * Initializing NSS with certpath: sql:/etc/pki/nssdb * CAfile: /etc/pki/tls/certs/ca-bundle.crt CApath: none * Server certificate: * subject: CN=cygwin.com,O=Red Hat Inc.,L=Raleigh,ST=North Carolina,C=US * start date: May 16 00:00:00 2014 GMT * expire date: May 20 12:00:00 2016 GMT * common name: cygwin.com * issuer: CN=DigiCert SHA2 High Assurance Server CA,OU=www.digicert.com,O=DigiCert Inc,C=US * NSS error -12276 (SSL_ERROR_BAD_CERT_DOMAIN) * Unable to communicate securely with peer: requested domain name does not match the server's certificate. * Closing connection 0 curl: (51) Unable to communicate securely with peer: requested domain name does not match the server's certificate.
This is a problem with nss_compat_ossl. It enables SSLv2, which is no longer supported by NSS. I will attach a patch to fix it.
Created attachment 897966 [details] [PATCH] Resolves: #1099423 - do not enable SSLv2 any more
ping?
Yes, attachment #897966 [details] needs to be applied.
nss_compat_ossl-0.9.6-9.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/nss_compat_ossl-0.9.6-9.fc20
nss_compat_ossl-0.9.6-9.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/nss_compat_ossl-0.9.6-9.fc21
nss_compat_ossl-0.9.6-9.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.
nss_compat_ossl-0.9.6-9.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.