Bug 2153 - Invalid SSL certificates on various Maemo sites
: Invalid SSL certificates on various Maemo sites
Status: CLOSED DUPLICATE of bug 1403
Product: maemo.org Website
: unspecified
: All All
: Low major (vote)
: ---
Assigned To: unassigned
: general@maemo.org
  Show dependency tree
Reported: 2007-10-23 07:27 UTC by Justin Dolske
Modified: 2007-11-30 11:30 UTC (History)
1 user (show)

See Also:



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

Description Justin Dolske (reporter) 2007-10-23 07:27:04 UTC
Firefox 3 new includes stricter checking of the certificates presented by SSL
sites, and makes it harder to view content that's improperly secured. [Instead
of a "blah blah blah [Ok]" prompt, you get a dead-end error page.] The goal is
to increase security, and remove  the ability for attackers to exploit people
who are not experts is decoding cryptic SSL warnings (ie, all of us :).

A number of maemo.org sites have certificate problems, which effectively makes
them unviewable in Firefox 3 today. Using Firefox 2 to visit these sites
results in a popup error, which is still a bad user experience.

A brief bit of poking around turned up the following:

...presents a cert for bugs.maemo.org

...presents a cert for maemo.org

https://www.maemo.org/  (https://maemo.org/ ok)
...presents a cert for maemo.org

...presents a cert for a248.e.akamai.net

...presents a cert for maemo.org

There might be others, someone with access to the server(s) should be able to
check the config and test. As I understand the issue, the usual fix for this
kind of problem is to obtain a certificate that's valid for multiple domains
and/or a wildcard domain ("*.maemo.org"). Or get individual certs for each
hostname, as used by working sites like https://downloads.maemo.org,
https://bugs.maemo.org, etc.
Comment 1 Quim Gil nokia 2007-10-23 07:47:47 UTC
Thanks for the details. I have just reopen a bug with had open with the same
issue. Let's concentrate there.

*** This bug has been marked as a duplicate of bug 1403 ***
Comment 2 Jake Kunnari 2007-11-30 11:30:13 UTC
Closing Duplicate bug reports. Please follow progress of issue from linked bug