From: Mark Wielaard <mark@klomp.org>
To: "Frank Ch. Eigler" <fche@elastic.org>,
Overseers mailing list <overseers@sourceware.org>
Cc: Ian Lance Taylor <iant@golang.org>
Subject: Re: frysk wiki has odd error message
Date: Wed, 16 Sep 2020 12:55:00 +0200 [thread overview]
Message-ID: <31c1c7d480310de2bbac4960887322644652db84.camel@klomp.org> (raw)
In-Reply-To: <20200915172802.GG15230@elastic.org>
Hi,
On Tue, 2020-09-15 at 13:28 -0400, Frank Ch. Eigler wrote:
> I tried to fix up the permissions, but then noticed that
> > /wiki/frysk/data/pages contains 30.000+ pages, almost all of which look
> > like spam. Sigh. Probably best to remove the whole wiki.
> > Note that the cgen and ecos wikis are in the same state.
>
> Yes, back before we locked down the moinmoin wikis with EditorGroup
> type ACLs, they were ALL inundated by spam, including the heavily used
> ones too like gcc.
>
> > Shall I simply remove those wikis?
> > Or does anybody want to try to clean them up?
>
> ... or can leave them as is, as long as there is no local link into
> the spam pages, people here won't be any wiser. Perhaps someone can
> figure out a way of despamming them at some point - doing it by hand
> is just too big a job.
OK. I left them as is and set the permissions on the pages directory to
rw for apache only. I couldn't edit any pages without being logged in
and couldn't create a new user (ecos simply never sent any email, frysk
and cgen threw an exception). Note that the ecos wiki is totally empty
at the moment (and redirects to ecos.sourceware.org/wiki).
Cheers,
Mark
prev parent reply other threads:[~2020-09-16 10:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-15 16:58 Ian Lance Taylor
2020-09-15 17:21 ` Mark Wielaard
2020-09-15 17:28 ` Frank Ch. Eigler
2020-09-16 10:55 ` Mark Wielaard [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=31c1c7d480310de2bbac4960887322644652db84.camel@klomp.org \
--to=mark@klomp.org \
--cc=fche@elastic.org \
--cc=iant@golang.org \
--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).