Update from 14:30 UTC: The problem is solved.

We want to let you know that we are aware about an invalid SSL certificate on some of our servers behind the https protocol. This is the case most of the time at least between 04:00 until 11:00 CET today.

We took down some of our services temporarily after getting aware of this. Affected services were

• build.opensuse.org
• api.opensuse.org
• hermes.opensuse.org
• notify.opensuse.org
• connect.opensuse.org
• features.opensuse.org

The issue is reported to our service provider maintaining the proxy who delivers this certificate.

I hope everybody of you will continue not to trust invalid certifications for our services. It can always be a man-in-the-middle-attack and especially when submitting passwords or sensitive data like source code it is not acceptable. So please continue to miss-trust invalid certificates on our servers.

Sorry

We will be updating our certificates for *.opensuse.org and *.suse.de today, sometime between 19:00 and 22:00 UTC.  We will be upgrading to a 2048 bit certificate, which will provide better security for the site.  We are also switching to a different vendor who can provide us more efficient support.  We plan on chaining the certificate up to the Entrust root CA.

It is possible that a small portion of the community may experience some issues with this switch.  Specifically, any system previous to SUSE 10 may not have the Entrust CA in its system certificate store.  For these systems, utilities such as wget may present an error when trying to pull a resource from opensuse.org over an SSL connection.  The solution is to either run wget with the “–no-check-certificate” option or to add the Entrust root to the system certificate store (found in /etc/ssl/certs).  Browsers and cURL use their own certificate store and should not be affected by this switch, even on older systems.

If anyone discovers an issue after we make the switch, please contact webmaster@opensuse.org.