Hi Flo, *,
On Mon, Sep 3, 2012 at 8:04 AM, Florian Effenberger
<floeff@documentfoundation.org> wrote:
[no captcha on new-account page in wiki]
does this error still occur? I just loaded the new account page and got the
captcha as expected.
Can reproduce here. Apparently browsers refuse to load the captcha
using https as the certificate for challenge.assira.com is not
trustworthy.
Probably won't occur on windows as the certificate is issues by
Microsoft's CA, but on linux with chromium, firefox and epiphany it is
reproducible.
Just try https://challenge.asirra.com/images/border5.gif and see for yourself.
Maybe that certificate in itself wouldn't be a problem, but the
javascript is loaded via http
<div class='captcha'><p>To help protect against automated account
creation, please solve the simple sum below and enter the answer in
the box (<a href="/Special:Captcha/help"
title="Special:Captcha/help">more info</a>):
</p><script src="http://challenge.asirra.com/js/AsirraClientSide.js"></script
And that makes the bells ring in the browser :-)
ciao
Christian
--
Unsubscribe instructions: E-mail to website+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/website/
All messages sent to this list will be publicly archived and cannot be deleted
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: 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.