https://bugs.freedesktop.org/show_bug.cgi?id=16687

--- Comment #12 from almos aaalmosss@gmail.com 2011-05-15 10:54:25 PDT --- Is this problem still around? According to comments #6 and #9 it is fixed in the currently preferred codepath (KMS/DRI2/EXA).

Sadly, Mozilla's opinion is that security comes from paying shitloads of money to VeriSign. Hopefully they'll see the sense in publishing the CACert CA, and we'll have a CACert certificate, which will validate.

This is a known design flaw of SSL. See http://blog.thoughtcrime.org/ssl-and-the-future-of-authenticity for more information.