Bug 576267 - NSS/SSL failing with: Remote Certificate has expired ... doesn't get to the user
Summary: NSS/SSL failing with: Remote Certificate has expired ... doesn't get to the user
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: yum
Version: 19
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Packaging Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-03-23 16:53 UTC by David Woodhouse
Modified: 2023-09-14 01:20 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-02-18 13:26:09 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description David Woodhouse 2010-03-23 16:53:06 UTC
[root@falcon nssdb]# yum update
Loaded plugins: presto, refresh-packagekit
00twosheds                                                                             | 4.2 kB     00:00 ... 
00twosheds-updates                                                                     | 4.4 kB     00:00 ... 
Error: Cannot retrieve repository metadata (repomd.xml) for repository: fedora. Please verify its path and try again

WTF?

If I set $URLGRABBER_DEBUG=1 before running yum, I get more useful information. But I shouldn't have do to that.

INFO:urlgrabber:opening local file "/var/cache/yum/i386/12/fedora/metalink.xml.tmp" with mode wb
* About to connect() to mirrors.fedoraproject.org port 443 (#0)
*   Trying 2610:28:200:1::fed0:2... * connected
* Connected to mirrors.fedoraproject.org (2610:28:200:1::fed0:2) port 443 (#0)
* warning: ignoring unsupported value (1) of ssl.verifyhost
*   CAfile: /etc/pki/tls/certs/ca-bundle.crt
  CApath: none
* Remote Certificate has expired.
* NSS error -8181
* Closing connection #0
* Peer certificate cannot be authenticated with known CA certificates
1917-06-07 01:08:55,-709 exception: [Errno 14] client cert cannot be verified or client cert incorrect
INFO:urlgrabber:exception: [Errno 14] client cert cannot be verified or client cert incorrect
1917-06-07 01:08:55,-706 retrycode (14) not in list [-1, 2, 4, 5, 6, 7], re-raising
INFO:urlgrabber:retrycode (14) not in list [-1, 2, 4, 5, 6, 7], re-raising
Error: Cannot retrieve repository metadata (repomd.xml) for repository: fedora. Please verify its path and try again

Comment 1 seth vidal 2010-03-23 17:05:00 UTC
look at the set of pkgs you just updated was 'nss' in there?

Comment 2 David Woodhouse 2010-03-23 17:17:37 UTC
This machine was installed yesterday with all current updates, and has nss-3.12.6-1.2.fc12.i686 installed.

There's been a lot of NSS breakage recently, but I don't think this failure is NSS's fault -- I'm assuming that the 'Remote Certificate has expired' line is telling the truth.

This bug is filed for the fact that I had to set $URLGRABBER_DEBUG in order to see that line.

Comment 3 James Antill 2010-03-25 14:59:24 UTC
I strongly suspect there is something different in NSS, as I can happily download rawhide metalink/etc. here ... but I've just heard from someone else running rawhide that they have the same problem.

Comment 4 David Woodhouse 2010-03-25 18:05:30 UTC
My clock was set to 1917. It's a slightly crappy error for NSS to give, but that's not the point -- the point in _this_ bug is that yum wasn't showing me anything useful at all.

Comment 5 James Antill 2010-03-25 21:29:27 UTC
Ahh, fiar enough. I wonder what the other guys problem was then.

And yeh, I changed the summary for the BZ to reflect the UI problem. And in this case it shouldn't be too hard to fix as urlgrabber has the error.

Comment 6 Bug Zapper 2010-11-03 18:48:30 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  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 WONTFIX if it remains open with a Fedora 
'version' of '12'.

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 prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 7 Bug Zapper 2010-12-03 16:51:56 UTC
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 8 David Woodhouse 2010-12-03 17:04:29 UTC
I believe the lack of appropriate error reporting is still present in current versions; reopening.

Comment 9 Fabian Deutsch 2011-11-13 12:29:05 UTC
It still happens todayand should be catched. See our current nss problem.

Comment 19 Fedora End Of Life 2013-04-03 20:16:11 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19

Comment 20 Fedora End Of Life 2015-01-09 21:42:57 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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 19 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.

Comment 21 Fedora End Of Life 2015-02-18 13:26:09 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.

Comment 22 Red Hat Bugzilla 2023-09-14 01:20:34 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days


Note You need to log in before you can comment on or make changes to this bug.