From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: [wiki] fake account spam
Date: Thu, 25 Apr 2013 13:46:32 -0400 (EDT) [thread overview]
Message-ID: <alpine.LNX.2.02.1304251344430.4279@ybpnyubfg.ybpnyqbznva> (raw)
In-Reply-To: <CAF=dkzyBFwTsnjZC6vQOHjYKKKk1MOOAmafwH=t4LLiKY3UKWQ@mail.gmail.com>
On Thu, 25 Apr 2013, Sietse Brouwer wrote:
> We're getting 3-12 new accounts created per day. If nothing else,
> they're cluttering up the recent changes list.
>
> I think it's a good idea to update the security questions --- it's
> easy to do, it'll probably work, and we can always move on to stronger
> measures that require more work. Below are some replacemetn questions.
>
> * If you have a log of which questions get answered correctly,
> perhaps only rotate out the bad question(s);
> * If finding the cracked questions is nontrivial (i.e. more work than
> 'just open the log file and see which ones get answered every day'),
> just replace them all.
>
> If this works, hooray; if it stops working, we can either change the
> questions again (if the spammers took long to get through) or move on
> to e.g. the ConfirmAccount extension [1,2] (if the questions got
> cracked quickly, so we are getting 'human' attention from the spammer
> instead of his bots).
Confirm account means that a new user will not be able to quickly correct
typos etc. Isn't there a simple way to add a captcha to mediawiki. I am
not a big fan of Captchas, but the are the de facto standard for human
verification. A user only has to do it once, so it is not too big of an
annoyance either.
Aditya
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2013-04-25 17:46 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-05 13:43 Philipp Gesang
2013-04-05 13:59 ` Mojca Miklavec
2013-04-05 14:09 ` Arthur Reutenauer
2013-04-06 1:18 ` Leo Arnold
2013-04-05 14:40 ` Alan BRASLAU
2013-04-06 14:53 ` Philipp Gesang
2013-04-25 17:31 ` Sietse Brouwer
2013-04-25 17:46 ` Aditya Mahajan [this message]
2013-04-25 21:52 ` Sietse Brouwer
2013-04-26 8:57 ` Alan BRASLAU
2013-04-26 9:32 ` Wolfgang Schuster
2013-04-26 9:44 ` Hans Hagen
2013-04-25 18:19 ` Thomas A. Schmitz
2013-04-25 21:07 ` Alan BRASLAU
2013-04-26 6:31 ` Procházka Lukáš Ing. - Pontex s. r. o.
2013-04-26 6:55 ` Thomas A. Schmitz
2013-04-26 7:37 ` Taco Hoekwater
2013-04-26 7:48 ` luigi scarso
2013-04-26 8:41 ` Alan BRASLAU
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=alpine.LNX.2.02.1304251344430.4279@ybpnyubfg.ybpnyqbznva \
--to=adityam@umich.edu \
--cc=ntg-context@ntg.nl \
--cc=taco@elvenkind.com \
/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).