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 F32BE3858032 for ; Fri, 28 Jul 2023 16:09:16 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org F32BE3858032 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=1690560556; 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=qGG9PwnrBMylCPVraAh7bcg1+XjvNdPxoSEShQnPx24=; b=N9QrR6FtjkwXdGDGOKvWvWeMQwjwBUcAkS9O12qLrJg9A6tX29/en9rI55Ss5sALDfhYKP h4nMJsqiNH2ZTMkAH+WW5iImmE8GXWPvKqCh63RIjLfAOmeVKhPEfLT9pFkqTzBigkTJsA YDgyKalJ+tVAwqwPIieyzM9D5tUrhH8= Received: from mimecast-mx02.redhat.com (66.187.233.73 [66.187.233.73]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-696-lpWRxSQCM4CdTD11HmVrWA-1; Fri, 28 Jul 2023 12:09:14 -0400 X-MC-Unique: lpWRxSQCM4CdTD11HmVrWA-1 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.rdu2.redhat.com [10.11.54.5]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id ABCB12A59577; Fri, 28 Jul 2023 16:09:13 +0000 (UTC) Received: from oldenburg3.str.redhat.com (unknown [10.39.194.91]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 389BBF782A; Fri, 28 Jul 2023 16:09:13 +0000 (UTC) From: Florian Weimer To: Siddhesh Poyarekar Cc: GNU C Library Subject: Re: GNU C Library as its own CNA? References: <1f5a1295-36d1-ab5e-86ec-1e91acefc63f@gotplt.org> Date: Fri, 28 Jul 2023 18:09:12 +0200 In-Reply-To: <1f5a1295-36d1-ab5e-86ec-1e91acefc63f@gotplt.org> (Siddhesh Poyarekar's message of "Fri, 28 Jul 2023 11:56:43 -0400") Message-ID: <87a5vgvx07.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.5 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain X-Spam-Status: No, score=-4.8 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,T_SCC_BODY_TEXT_LINE 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: * Siddhesh Poyarekar: > At the outset, we'll need to have broad agreement on the following: > > 1. How should users submit issues? We would need an independent, > private mailing list, possibly one that can also do PGP for users to > report security issues. > > 2. Identify a group of people who ought to be on that list. A > starting group could be a cross section of named maintainers from > various distributions and FSF stewards but we probably need a way to > make sure that the group is inclusive without being too broad. > > 3. A formal representation to the root CNA, i.e. Red Hat. We would > need a group of volunteers that would be willing to step in as signees > for this. I'm in, but I can't do it alone and would need more > volunteers; it could perhaps be the same set of people who would be > part of the initial security team in (2). I think the CNA rules sort of assume that a CNA issues security advisories: So we'd have to start doing that, too. Thanks, Florian