Does anyone know if it is possible to purchase a 'real' SSL certificate for our domain? I would be willing to contribute some money directly towards fixing this issue.
On Fri, Feb 4, 2011 at 10:53 AM, emarkay <[email protected]> wrote: > > OK, it's a Firefox and CA Cert issue, and the best answer seems to be: > > "Known problem related to the free cert used. For some reason browsers do > not accept the cert which leads to the report." > > However the workaround: "(you can also use regular http if you don't want to > trust an untrusted > certificate :-)) " still gives the aforementioned warning error. > > I am not paranoid about a bogus script and/or a buggy browser, or the > politics and all that, but someone needs to stand up and fix this. > > Either remove the "https", get a "real" certificate, post a workaround, or > at least have a "We know ... ignore ... you are safe..." pre-page, or > something. > > Not off to a good start for those lesser aware noobs, now aren't we, IMHO? > > MRK > > > > > -- > View this message in context: > http://nabble.documentfoundation.org/This-Connection-is-Untrusted-I-know-I-know-but-tp2420227p2420227.html > Sent from the Website mailing list archive at Nabble.com. > > -- > Unsubscribe instructions: E-mail to [email protected] > List archive: http://listarchives.libreoffice.org/www/website/ > *** All posts to this list are publicly archived for eternity *** > > -- Unsubscribe instructions: E-mail to [email protected] List archive: http://listarchives.libreoffice.org/www/website/ *** All posts to this list are publicly archived for eternity ***
