From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gnu.wildebeest.org (gnu.wildebeest.org [45.83.234.184]) by sourceware.org (Postfix) with ESMTPS id 0054A3858C60 for ; Mon, 10 Jan 2022 18:09:06 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 0054A3858C60 Received: from tarox.wildebeest.org (83-87-18-245.cable.dynamic.v4.ziggo.nl [83.87.18.245]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by gnu.wildebeest.org (Postfix) with ESMTPSA id DED793048E27; Mon, 10 Jan 2022 19:09:04 +0100 (CET) Received: by tarox.wildebeest.org (Postfix, from userid 1000) id D3FC5413E102; Mon, 10 Jan 2022 19:09:03 +0100 (CET) Message-ID: <00d03042f9454ba08851ad25e4cea164e02faba5.camel@klomp.org> Subject: Re: Request for a new Sourceware Bugzilla account. From: Mark Wielaard To: Overseers mailing list Cc: George Dhmosxakhs Date: Mon, 10 Jan 2022 19:09:03 +0100 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Evolution 3.28.5 (3.28.5-10.el7) Mime-Version: 1.0 X-Spam-Status: No, score=-4.1 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: overseers@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Overseers mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jan 2022 18:09:08 -0000 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:=20 https://sourceware.org/glibc/wiki/Security%20Process#Reporting_private_secu= rity_bugs Cheers, Mark