From: Mark Wielaard <mark@klomp.org>
To: Overseers mailing list <overseers@sourceware.org>
Cc: George Dhmosxakhs <dimosxakis0@gmail.com>
Subject: Re: Request for a new Sourceware Bugzilla account.
Date: Mon, 10 Jan 2022 19:09:03 +0100 [thread overview]
Message-ID: <00d03042f9454ba08851ad25e4cea164e02faba5.camel@klomp.org> (raw)
In-Reply-To: <CAKt3386n27uX1gfUqVMtg2sBd5s-EJuoTti5B=hurgCqUqU3wA@mail.gmail.com>
Hi George,
On Mon, 2022-01-10 at 18:48 +0200, George Dhmosxakhs via Overseers
wrote:
> I'm trying to register a new account but I get a restricted error
> message: "User account creation has been restricted.".
> I would like to create an account to report a security issue in glibc
> which I found.
A bugzilla account has been created for you. You should have an email
about it. You can activate it through the Forgot/Reset password link.
Note that sourceware bugzilla bugs are public by default.
If you believe the security issue should be handled privately please
see:
https://sourceware.org/glibc/wiki/Security%20Process#Reporting_private_security_bugs
Cheers,
Mark
prev parent reply other threads:[~2022-01-10 18:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-10 16:48 George Dhmosxakhs
2022-01-10 18:09 ` 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=00d03042f9454ba08851ad25e4cea164e02faba5.camel@klomp.org \
--to=mark@klomp.org \
--cc=dimosxakis0@gmail.com \
--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).