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/77319] [bugzilla] bugzilla behaves erratically
Date: Mon, 22 Aug 2016 17:51:00 -0000	[thread overview]
Message-ID: <bug-77319-5127-DiUfRLS5cO@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-77319-5127@http.gcc.gnu.org/bugzilla/>

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

Frédéric Buclin <LpSolit at netscape dot net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |overseers at gcc dot gnu.org

--- Comment #3 from Frédéric Buclin <LpSolit at netscape dot net> ---
I do not plan to relax user account creation for now. Logs show that spammers
still try to create accounts again and again. Many of them are caught due to
their IP address (banned), but many random IP addresses are also used to create
such accounts (and looking at the email addresses used lets no doubt on the
purpose of the accounts).

So despite I implemented anti-spam features in Bugzilla itself, which does its
job for now, restricting user account creation still prevents a lot of attacks.

I still want to implement bug 72856 before relaxing user account creation.

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

       reply	other threads:[~2016-08-22 17:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-77319-5127@http.gcc.gnu.org/bugzilla/>
2016-08-22 17:51 ` LpSolit at netscape dot net [this message]
2016-08-22 18:32 ` fche at redhat dot com
2016-09-10 17:15 ` pinskia at gcc dot gnu.org

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-77319-5127-DiUfRLS5cO@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).