public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Andrew Pinski <pinskia@gmail.com>
Cc: Overseers mailing list <overseers@sourceware.org>,
	Joel Brobecker <brobecker@adacore.com>,
	Simon Marchi <simon.marchi@polymtl.ca>,
	Pedro Alves <pedro@palves.net>
Subject: Re: getting spammed on bugzilla
Date: Fri, 12 Nov 2021 08:40:33 +0400	[thread overview]
Message-ID: <YY3wQQQ/R/th3Dki@adacore.com> (raw)
In-Reply-To: <CA+=Sn1k3GWexDuxMnmbj-zPGboLanzUGNpAH8mth_BH17vuEyA@mail.gmail.com>

> > > LLVM has solved this by disabling new user self-registration:
> > >
> > >   https://bugs.llvm.org/enter_bug.cgi
> > >
> > > "New user self-registration is disabled due to spam. For an account please email
> > > bugs-admin@lists.llvm.org
> > > with your e-mail address and full name."
> >
> > I'm happy to help with answering those legitimate account
> > creations, if that makes a differnce.
> >
> > Any other ideas, perhaps?
> 
> GCC already disables new account creation; while sourceware does not.
> I know the gcc bugzilla did get some spam last week and even at that
> point, the account had been created manually too (GCC has had new
> accounts disable for over a few years now even).
> So what looked like a legitimate request and turned out not to be, did
> slip through.  Fixing that is hard really.

Interesting. Thanks for sharing Andrew.

My thinking on this is that we should try doing the same for
sourceware's bugzilla, and see how it goes. I'm hoping the extra
step will be a high enough barrier that it'll encourage the majority
of spammers to find somewhere else to go. Even if not perfect, if
we can block the majority of spam, that'll already be a great win
for us.

-- 
Joel

  reply	other threads:[~2021-11-12  4:40 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-11  3:29 Joel Brobecker
2021-11-11  3:47 ` Andrew Pinski
2021-11-12  4:40   ` Joel Brobecker [this message]
2021-11-12  8:55     ` Mark Wielaard
2021-11-12 13:26       ` Carlos O'Donell
2021-11-22  4:03         ` Joel Brobecker
2021-11-24 10:09           ` Mark Wielaard
2021-11-24 14:55             ` Frank Ch. Eigler
2021-11-24 23:40               ` Mark Wielaard
2021-11-25  0:19                 ` Frank Ch. Eigler
2021-11-25 17:49                   ` Joseph Myers
2021-11-25 17:54                     ` Frank Ch. Eigler
2021-11-25 17:59                       ` Joseph Myers
2021-11-28 17:01                   ` Mark Wielaard
2021-11-28 17:35                     ` Frank Ch. Eigler
2021-11-28 18:07                       ` Mark Wielaard
2021-11-29 17:12                         ` Joseph Myers
2021-12-17  2:50                           ` Joel Brobecker
2021-12-17 17:19                             ` Frank Ch. Eigler

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=YY3wQQQ/R/th3Dki@adacore.com \
    --to=brobecker@adacore.com \
    --cc=overseers@sourceware.org \
    --cc=pedro@palves.net \
    --cc=pinskia@gmail.com \
    --cc=simon.marchi@polymtl.ca \
    /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).