From: "H. Langos" <henrik-dvb@prak.org>
To: Johannes Stezenbach <js@linuxtv.org>
Cc: linux-media@vger.kernel.org
Subject: Re: wiki on linixtv.org locked
Date: Mon, 27 Apr 2009 22:29:25 +0200 [thread overview]
Message-ID: <20090427202925.GO2895@www.viadmin.org> (raw)
In-Reply-To: <20090427173741.GA20847@linuxtv.org>
hi johannes,
thank you for your quick reply.
On Mon, Apr 27, 2009 at 07:37:41PM +0200, Johannes Stezenbach wrote:
> On Mon, Apr 27, 2009 at 06:43:21PM +0200, H. Langos wrote:
> >
> > Yesterday a stupid kid vandalized a bunch of pages on the linuxtv wiki and
> > a sysop locked to database to undo the damage.
> ...
> The damage was done by a bot script and it affected as many pages
> as the edit rate limiter would allow it to do until I noticed it.
> If you search for "GRAWP'S MASSIVE" you'll see this is not
> limited to linuxtv.org.
ah, ok .. so it is a stupid kid with scripting knowledge. :-)
> > Anyway .. Now, after about 24h the wiki is still locked.
> > Any reason for that?
>
> It is locked until I had time to take measures to prevent
> similar damage from happening again right away. I'm
> open to suggestions if someone has experience with this.
first of all. please, replace "sigh..." with a more informative locking
message.
the next step would be to update the mediwiki software to 1.11.1 if you have
$wgEnableAPI = true, that is. (i know it is only a XSS that hits internet
explorer users .. but hey, they are people, too ;-)
if i remember right, the linuxtv wiki only allows editing to registered
users. therefore you could simply temporarily disable new user registration
and enable editing again for registered users.
then i'd suggest installing the reCAPTCHA extention. not only will it
prevent bots from registering, you also help to digitize old books.
http://recaptcha.net/plugins/mediawiki/
with that in place you can re-enable new user registration. you can even
make logins optional and require captcha solving for anonymous edits. this
would probably improve the wiki in general as new users would not jump through
yet another loop just in order to help other users... i know, new users can
cost more time than they are worth but hope springs eternaly :-)
cheers
-henrik
next prev parent reply other threads:[~2009-04-27 20:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-27 16:43 wiki on linixtv.org locked H. Langos
2009-04-27 17:37 ` Johannes Stezenbach
2009-04-27 20:29 ` H. Langos [this message]
2009-04-27 22:14 ` Johannes Stezenbach
2009-04-27 23:21 ` H. Langos
2009-04-28 8:20 ` Johannes Stezenbach
2009-04-28 8:25 ` H. Langos
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=20090427202925.GO2895@www.viadmin.org \
--to=henrik-dvb@prak.org \
--cc=js@linuxtv.org \
--cc=linux-media@vger.kernel.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