Guy Voets schrieb:
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.
Thanks David for the explanation.
By that: is LibO also with CAcert?
Unsubscribe instructions: Email to firstname.lastname@example.org
Posting guidelines: http://netmeister.org/news/learn2quote.html
*** All posts to this list are publicly archived ***
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