qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Weil <sw@weilnetz.de>
To: QEMU Developers <qemu-devel@nongnu.org>
Cc: Anthony Liguori <aliguori@us.ibm.com>, Michael Tokarev <mjt@tls.msk.ru>
Subject: Re: [Qemu-devel] Problem editing wiki page in wiki.qemu.org
Date: Sun, 18 Dec 2011 12:20:01 +0100	[thread overview]
Message-ID: <4EEDCC61.90904@weilnetz.de> (raw)
In-Reply-To: <CAFEAcA_sZXe=RVV2Xoi_2eZHBGNBRT8BKwohx-dDTt-LHd9vGQ@mail.gmail.com>

Am 18.12.2011 11:44, schrieb Peter Maydell:
> On 18 December 2011 10:38, Orit Wasserman <owasserm@redhat.com> wrote:
>> Hi Anthony,
>> I'm trying to edit a wiki page I create in qemu.org.
>>
>> I get the following error:
>
>> Intended blockee: 127.0.0.1
>
>> Your current IP address is 127.0.0.1, and the block ID is #132.
>
> This looks very fishy ^^^^^
>
> I get the same error, and I suspect everybody will.
> It looks like the wiki thinks we all access it from
> localhost now :-)
>
> -- PMM

It looks like the autoblock was created yesterday and
terminates automaticallytoday (see
http://wiki.qemu.org/index.php?title=Special:BlockList&action=search&ip=%23132).

That won't help much as long as the wiki thinks that everyone
has the localhost address because the next autoblock will
block all users again.

Are block lists really useful to protect the QEMU wiki?
Neither user names nor IP addresses are unique.
Spammerscan create any number of new names.

Regards,
Stefan Weil

  parent reply	other threads:[~2011-12-18 11:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-18 10:38 [Qemu-devel] Problem editing wiki page in wiki.qemu.org Orit Wasserman
2011-12-18 10:44 ` Peter Maydell
2011-12-18 10:55   ` 陳韋任
2011-12-18 11:20   ` Stefan Weil [this message]
2011-12-18 11:45     ` Michael Tokarev
2011-12-19  9:54       ` Stefan Hajnoczi

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=4EEDCC61.90904@weilnetz.de \
    --to=sw@weilnetz.de \
    --cc=aliguori@us.ibm.com \
    --cc=mjt@tls.msk.ru \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).