From: Daniel Berlin <dberlin@dberlin.org>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: Joel Brobecker <brobecker@adacore.com>,
overseers@sourceware.org, Daniel Jacobowitz <drow@false.org>
Subject: Re: abusive user of GDB Wiki for spam ...
Date: Wed, 22 Dec 2010 01:43:00 -0000 [thread overview]
Message-ID: <AANLkTi=GppG1XP14hnSi-eXxNoKeY7Dqhh-qpkvE0SXw@mail.gmail.com> (raw)
In-Reply-To: <20101216221104.GG9812@redhat.com>
On Thu, Dec 16, 2010 at 5:11 PM, Frank Ch. Eigler <fche@redhat.com> wrote:
>
> Hi -
>
> On Thu, Dec 16, 2010 at 04:05:23PM +0400, Joel Brobecker wrote:
> > [...]
> > The first thing I would do is delete these files (added to page
> > "rutud"). This requires special priviledges.
>
> I zapped the files by low level fs ops. Your wiki userid is now an
> 'admin' and should have despam privileges, if that's quite enough.
>
> > The second thing is probably start a discussion with the other
> > GDB maintainers as to decide what to do to prevent this sort of
> > abuse. [...]
>
> The easiest option is to disable wiki attachments by default, by
> adding
>
> actions_excluded = [u'AttachFile']
>
> into the /wiki/PROJECT.py file. Whether that can be enabled again on
> a per-user basis, or whether an admin would have to hand-edit the file
> again to turn on attachments briefly, I dunno. Unfortunately, I have
> so far found no better option with moinmoin. Switching to another
> wiki software (mediawiki?) is an option.
At the point we switched from phpwiki, mediawiki was fairly difficult to setup.
If it's not so hard anymore, i'm pretty positive mediawiki has a
moinmoin importer, and supports recaptcha
>
> - FChE
next prev parent reply other threads:[~2010-12-17 1:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-27 16:53 Joel Brobecker
2010-11-27 17:00 ` Frank Ch. Eigler
2010-12-16 12:05 ` Joel Brobecker
2010-12-17 4:05 ` Joel Brobecker
2010-12-22 1:32 ` Frank Ch. Eigler
2010-12-22 1:43 ` Daniel Berlin [this message]
2010-12-22 6:44 ` Joel Brobecker
2011-01-03 20:54 ` Frank Ch. Eigler
2011-01-04 4:51 ` Joel Brobecker
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='AANLkTi=GppG1XP14hnSi-eXxNoKeY7Dqhh-qpkvE0SXw@mail.gmail.com' \
--to=dberlin@dberlin.org \
--cc=brobecker@adacore.com \
--cc=drow@false.org \
--cc=fche@redhat.com \
--cc=overseers@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).