From: Jonas Maebe <jonas.maebe@elis.ugent.be>
To: Joel Brobecker <brobecker@adacore.com>
Cc: "Frank Ch. Eigler" <fche@redhat.com>,
Stan Shebs <stanshebs@earthlink.net>,
gdb@sourceware.org
Subject: Re: [GDB Wiki] Add editor privilege control
Date: Wed, 09 Apr 2014 13:12:00 -0000 [thread overview]
Message-ID: <42515698-A91E-47AB-8FDB-27036DA72E40@elis.ugent.be> (raw)
In-Reply-To: <20140409125330.GA21704@adacore.com>
On 09 Apr 2014, at 14:53, Joel Brobecker wrote:
> Frank - Do you know what would need to be done at the technical
> level to protect ourselves? I would think we first create a
> EditorGroup
> page in the wiki, then add the corresponding group and its privileges
> in the wiki's configuration, right? Or can everything be done directly
> from the wiki? Anything else we should be doing?
A very useful protection against spammers for our wiki that I've found
is using the stopforumspam.com blacklist. It's specifically geared at
stopping wiki/forum spammers and works much better than more generic
blacklists such as the Spamhaus XBL. Here's how to use it in MediaWiki/
PHP:
if(isset($_SERVER['remote_addr']) && ereg('yes', file_get_contents('http://www.stopforumspam.com/api?ip='
. $_SERVER['remote_addr'])))
{
<it's a blacklisted IP>
}
I know neither PHP nor Python very well (I got the above code from
somewhere else), so I can't translate it, but I'm sure you get the
gist. As long as you
a) forbid editing by anonymous users
b) perform the above check at account creation time and whenever
someone tries to add a link to an article
you should be pretty safe. I've had only 3 potentially bogus account
registrations and not a single instance of spam on our wiki since I
started using that blacklist 10 days ago. You can use it freely,
except if you have more than 20000 queries per day (we have about 200
account creation attempts per hour on average, sometimes spiking to
over a 1000). In that case you should download snapshots of their
database and use that instead, as explained at http://www.stopforumspam.com/downloads/
Jonas
next prev parent reply other threads:[~2014-04-09 13:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-14 3:08 Joel Brobecker
2014-02-14 7:12 ` Eli Zaretskii
2014-02-14 7:26 ` Joel Brobecker
2014-02-14 18:35 ` Stan Shebs
2014-02-14 20:58 ` Doug Evans
2014-02-15 2:52 ` Joel Brobecker
2014-03-02 15:35 ` Frank Ch. Eigler
2014-03-03 16:12 ` Joel Brobecker
2014-04-09 12:53 ` Joel Brobecker
2014-04-09 13:12 ` Jonas Maebe [this message]
2014-04-09 13:34 ` Frank Ch. Eigler
2014-04-09 18:24 ` Joel Brobecker
2014-04-09 17:44 ` Stan Shebs
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=42515698-A91E-47AB-8FDB-27036DA72E40@elis.ugent.be \
--to=jonas.maebe@elis.ugent.be \
--cc=brobecker@adacore.com \
--cc=fche@redhat.com \
--cc=gdb@sourceware.org \
--cc=stanshebs@earthlink.net \
/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