All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Weil <sw@weilnetz.de>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] The mainpage of QEMU.org is attacked?
Date: Fri, 04 Nov 2011 08:32:16 +0100	[thread overview]
Message-ID: <4EB39500.3090608@weilnetz.de> (raw)
In-Reply-To: <4EB3544B.6090303@us.ibm.com>

Am 04.11.2011 03:56, schrieb Anthony Liguori:
> On 11/03/2011 09:43 PM, Zhi Yong Wu wrote:
>> HI,
>>
>> Just now i found that the mainpage of QEMU.org is hacked, right?
>> http://wiki.qemu.org/Main_Page
>
> Not hacked, it's a wiki, so it's vulnerable to spam.  Folks have been 
> doing a great job reverting the spam.
>
> It amazes me that the spambots are beating the captcha so easily :-/
>
> I've protected the front page for now as I think this is happening 
> repeatedly.
>
> Regards,
>
> Anthony Liguori

I suggest more restrictions for new user accounts to reduce wiki spam.

These mediawiki extensions require more reasonable user names
and account confirmation:

http://www.mediawiki.org/wiki/Extension:ConfirmAccount
http://www.mediawiki.org/wiki/Extension:AntiSpoof

For someone who is really interested in contributing to the QEMU wiki,
account confirmation should be acceptable, and we could be sure
that there is at least a valid mail address connected to the new account.

The rate of valid account request will be much less than the
current rate of new spammer accounts and their bad contributions,
so the work required to process them is less than the current
work to remove spam.

Regards,
Stefan Weil

      parent reply	other threads:[~2011-11-04  7:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-04  2:43 [Qemu-devel] The mainpage of QEMU.org is attacked? Zhi Yong Wu
2011-11-04  2:56 ` Anthony Liguori
2011-11-04  2:59   ` Zhi Yong Wu
2011-11-04  7:32   ` Stefan Weil [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4EB39500.3090608@weilnetz.de \
    --to=sw@weilnetz.de \
    --cc=aliguori@us.ibm.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.