SSL certificate for bugs.maemo.org expired; over a week and still not fixed
bugs.maemo.org hosts the Bugzilla issue tracking system for Maemo, maemo.org and various Extras products. For security, communication is over HTTPS - so that transfered data (usernames, passwords, etc.) is protected from sniffing and replay attacks. On 17th July its SSL certificate -- the digital signature which lets your browser know it's talking to your bank, or your bug system -- expired. Typically, renewal would happen before the certificate expired so that users wouldn't see dire warnings from their browsers, unfortunately, that hasn't happened here. In bug #10951, Andre Klapper said, There's nothing that the *maemo.org team* currently can do here. Nokia is aware of this problem since Monday, 19th. They are working on it and I ping from time to time as fixing should not take that long but obviously does (don't ask me why). Users can bypass the security warnings from their browsers, but encouraging them to do so reduces the overall security of the web, and the users of maemo.org. If people think that invalid certificates are "OK" to ignore, they'll do so when their bank's website has been compromised. If Nokia are the hold up here (because, say, the certificates for maemo.org are purchased through a central department), they are causing excessive risk to their users and putting a barrier between developers and their users at a time when Maemo still needs active developers. One is left wondering, though, that since this has happened before when certificates expire why the maemo.org team didn't start the process with a suitable window before the certificate expired.