Re: [tdf-discuss] About Cacert SSL certificates (was: Feature request for 3.3 still possible?)

2010/11/9 David Nelson <commerce@traduction.biz>:
> Hi Guy, :-)
>
> On Tue, Nov 9, 2010 at 18:13, Guy Voets <nimantuis@gmail.com> 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
> > continue.
>
> 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
> you.
>
> I've seen this question posted before a few times, so I'll post this
> answer in a dedicated thread. HTH.
>
> David Nelson

Thanks David for the explanation.
And sorry for hijacking instead of starting a new thread about this

-- 
Guy
using LibO 3.3.0 on a iMac Intel DualCore Snow Leopard
-- please reply only to users@libreoffice.org --
Dodoes can't afford to have headaches

-- 
Unsubscribe instructions: Email to discuss+help@documentfoundation.org
Posting guidelines: http://netmeister.org/news/learn2quote.html
Archive: http://www.documentfoundation.org/lists/discuss/
*** All posts to this list are publicly archived ***