Hi Guy, :-)
On Tue, Nov 9, 2010 at 18:13, Guy Voets <firstname.lastname@example.org> wrote:
You have asked SeaMonkey to connect securely to bugs.freedesktop.org,
but we can't confirm that your connection is secure.
Normally, when you try to connect securely, sites will present trusted
identification to prove that you are going to the right place.
However, this site's identity can't be verified.
What Should I Do?
If you usually connect to this site without problems, this error could
mean that someone is trying to impersonate the site, and you shouldn't
It's happening because the project is using a free certificate
provider (http://cacert.org). Cacert is not configured in most
browsers as one of the "trusted providers". However, technically,
their certificates do their job just fine. It's a "political" thing.
Certificates are sold by corporations such as Verisign for quite a lot
of money, and the big boys don't like a free provider like Cacert
spoiling their otherwise-captive market. Don't worry, you can accept
the certificate and add it to your browser's list of trusted
providers. Neither Cacert nor the bug tracker site is trying to scam
I've seen this question posted before a few times, so I'll post this
answer in a dedicated thread. HTH.
Unsubscribe instructions: Email to email@example.com
Posting guidelines: http://netmeister.org/news/learn2quote.html
*** All posts to this list are publicly archived ***
- [tdf-discuss] About Cacert SSL certificates (was: Feature request for 3.3 still possible?) · David Nelson
Impressum (Legal Info)
: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (MPLv2
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our trademark policy