public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: "LpSolit at netscape dot net" <gcc-bugzilla@gcc.gnu.org>
To: overseers@gcc.gnu.org
Subject: [Bug web/72856] Trottle bug creation for newly created accounts (to limit spam)
Date: Wed, 10 Aug 2016 12:04:00 -0000	[thread overview]
Message-ID: <bug-72856-5127-c0ifbpfeMs@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-72856-5127@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=72856

--- Comment #4 from Frédéric Buclin <LpSolit at netscape dot net> ---
(In reply to Manuel López-Ibáñez from comment #3)
> I wonder about the effort required to do such a thing. Some of those emails
> seem fake, is there some kind of confirmation email for newly created
> accounts?

Yes. When a user requests a new account, an email is sent to that email
address, and the user must click on the link which is in the email to confirm
that 1) the email address is valid, and 2) it belongs to the user who wants to
create the bugzilla account. Clicking on this link will display a page where
the user must type his new password, and only after that is the bugzilla
account activated. It is not possible to create bugzilla accounts automatically
using the API (to prevent such problems).


> Limiting the number of bug reports per new account seems a good measure, but
> also easily circumvented as long as someone can create as many new users as
> they wish and each user stays below the limit.

I agree, that's a problem. But I think there isn't one single solution which
fixes all cases, but rather multiple solutions which, when combined together,
can give a reasonable level of spam prevention.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2016-08-10 12:04 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-10  2:43 [Bug web/72856] New: " LpSolit at netscape dot net
2016-08-10  2:44 ` [Bug web/72856] " LpSolit at netscape dot net
2016-08-10  5:50 ` trippels at gcc dot gnu.org
2016-08-10  8:33 ` gerald at pfeifer dot com
2016-08-10 11:46 ` manu at gcc dot gnu.org
2016-08-10 12:04 ` LpSolit at netscape dot net [this message]
2016-08-10 12:33 ` LpSolit at netscape dot net
2016-08-10 12:41 ` fche at redhat dot com
2016-08-11 11:58 ` joseph at codesourcery dot com
2016-08-15 19:57 ` redi at gcc dot gnu.org
2016-08-16 14:41 ` LpSolit at netscape dot net
2016-08-22 20:10 ` bernd.edlinger at hotmail dot de
2016-08-23  6:07 ` [Bug web/72856] Throttle " gerald at pfeifer dot com

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=bug-72856-5127-c0ifbpfeMs@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=overseers@gcc.gnu.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).