From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by sourceware.org (Postfix) with ESMTPS id D5EB53858C20 for ; Wed, 6 Sep 2023 12:33:42 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org D5EB53858C20 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=redhat.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=redhat.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1694003622; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=BY+oLTNveqWDxoq77O5dJIlLszHnlqPjYUZcXYe4g1w=; b=GnOU0HQIF3iTc7/Z/lBFAuAOUmYhZ19BZfxHFyPhB8MTq0ZbZ3ZOoCPz0foKTEkzq8+0Bx 0YCA2mqM078vWugtLcjsTq8jcmhGJAr3XkjWfK5zJcPDBturcOsRUiWr7Ae7h6/cO40/Ey LMmMEMMqgMMrgVE7yULJhq1EwQlcEFI= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-460-7RGy9AWSMg-zw78oleIAnQ-1; Wed, 06 Sep 2023 08:33:38 -0400 X-MC-Unique: 7RGy9AWSMg-zw78oleIAnQ-1 Received: from smtp.corp.redhat.com (int-mx08.intmail.prod.int.rdu2.redhat.com [10.11.54.8]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 57DBF803470; Wed, 6 Sep 2023 12:33:38 +0000 (UTC) Received: from oldenburg3.str.redhat.com (unknown [10.39.195.19]) by smtp.corp.redhat.com (Postfix) with ESMTPS id D8444C15BB8; Wed, 6 Sep 2023 12:33:37 +0000 (UTC) From: Florian Weimer To: Paul Eggert Cc: libc-alpha@sourceware.org Subject: Re: GNU C Library as its own CNA? References: <1f5a1295-36d1-ab5e-86ec-1e91acefc63f@gotplt.org> <6ad61af4-8890-809c-d168-5a6e8c750d26@cs.ucla.edu> Date: Wed, 06 Sep 2023 14:33:36 +0200 In-Reply-To: <6ad61af4-8890-809c-d168-5a6e8c750d26@cs.ucla.edu> (Paul Eggert's message of "Fri, 28 Jul 2023 10:28:46 -0700") Message-ID: <8734zrzdjz.fsf@oldenburg3.str.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.2 (gnu/linux) MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.1 on 10.11.54.8 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain X-Spam-Status: No, score=-4.5 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,KAM_SHORT,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H4,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE,SPF_NONE,TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: * Paul Eggert: > On 2023-07-28 09:41, Joseph Myers wrote: >> If we add some kind of private submission >> mechanism, we should also strongly discourage its use for the bulk of >> low-risk issues to avoid adding unnecessary overhead for those. > > One possibility is to use an already-existing submission mechanism, > namely the GNU Security Escalation Contact . For > what it's worth, that mailing list gets little email, mostly false > alarms. > > https://savannah.gnu.org/mail/?group=security That's not the documented purpose of : | Security Team | | The Security Team helps to resolve security bugs in | a timely fashion. If the maintainer of a GNU package fails to respond | to a report of a security flaw, the reporter can escalate the issue to | the security team. If it decides the issue is urgent, it can develop a | patch and publish a fixed release of the package. Maintainers can also | ask the security team for advice in securing their packages. | | New members are recruited from existing GNU volunteers when needed. It's clearly not intended as an external first point of contact. Thanks, Florian