Also, just checked with GitHub. In WEB-INF/update_center_rootCAs, the community CA is two years old and the update center root CA will be a year old tomorrow (April 19th).
I'm guessing that this isn't a mirror causing anything, just the dev team forgetting to generate new certificates on time. --Rob -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Mandeville, Rob Sent: Wednesday, April 18, 2012 1:32 PM To: '[email protected]' Subject: RE: Updates site with old certificate Getting the same thing hitting http://updates.jenkins-ci.org/update-center.json. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of jan-ruzicka Sent: Wednesday, April 18, 2012 1:12 PM To: Jenkins Users Subject: Updates site with old certificate Hi The update center [1] was showing exception[2] on certificate verification this morning. My guess is that one of the mirrors had an old certificate. Is there a way to find out which mirror caused this? Thanks Jan [1](hudson.model.UpdateSite doPostBack) [2] ... Signature verification failed in the update center 'default' <a href='#' class='showDetails'> ... Caused by: java.security.cert.CertificateExpiredException: NotAfter: Wed Apr 18 03:35:04 EDT 2012 The information in this message is for the intended recipient(s) only and may be the proprietary and/or confidential property of Litle & Co., LLC, and thus protected from disclosure. If you are not the intended recipient(s), or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any use, dissemination, distribution or copying of this communication is prohibited. If you have received this communication in error, please notify Litle & Co. immediately by replying to this message and then promptly deleting it and your reply permanently from your computer.
