Return-Path: Authentication-Results: lists.ozlabs.org; spf=none (mailfrom) smtp.mailfrom=linux.vnet.ibm.com (client-ip=148.163.158.5; helo=mx0a-001b2d01.pphosted.com; envelope-from=jrey@linux.vnet.ibm.com; receiver=) Authentication-Results: lists.ozlabs.org; dmarc=none (p=none dis=none) header.from=linux.vnet.ibm.com Received: from mx0a-001b2d01.pphosted.com (mx0b-001b2d01.pphosted.com [148.163.158.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 4360Fv14MtzDrPr for ; Sat, 1 Dec 2018 03:29:06 +1100 (AEDT) Received: from pps.filterd (m0098419.ppops.net [127.0.0.1]) by mx0b-001b2d01.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id wAUGPRrh020906 for ; Fri, 30 Nov 2018 11:29:04 -0500 Received: from e13.ny.us.ibm.com (e13.ny.us.ibm.com [129.33.205.203]) by mx0b-001b2d01.pphosted.com with ESMTP id 2p35y3rdvr-1 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=NOT) for ; Fri, 30 Nov 2018 11:29:03 -0500 Received: from localhost by e13.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Fri, 30 Nov 2018 16:29:02 -0000 Received: from b01cxnp23032.gho.pok.ibm.com (9.57.198.27) by e13.ny.us.ibm.com (146.89.104.200) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256/256) Fri, 30 Nov 2018 16:29:00 -0000 Received: from b01ledav005.gho.pok.ibm.com (b01ledav005.gho.pok.ibm.com [9.57.199.110]) by b01cxnp23032.gho.pok.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id wAUGSxQv19202262 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for ; Fri, 30 Nov 2018 16:28:59 GMT Received: from b01ledav005.gho.pok.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 11F4FAE05C for ; Fri, 30 Nov 2018 16:28:59 +0000 (GMT) Received: from b01ledav005.gho.pok.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id CFBF0AE05F for ; Fri, 30 Nov 2018 16:28:58 +0000 (GMT) Received: from ltc.linux.ibm.com (unknown [9.16.170.189]) by b01ledav005.gho.pok.ibm.com (Postfix) with ESMTP for ; Fri, 30 Nov 2018 16:28:58 +0000 (GMT) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Fri, 30 Nov 2018 10:32:36 -0600 From: Joseph Reynolds To: openbmc@lists.ozlabs.org Subject: Application to become a CVE Numbering Authority (CNA) X-Sender: jrey@linux.vnet.ibm.com User-Agent: Roundcube Webmail/1.0.1 X-TM-AS-GCONF: 00 x-cbid: 18113016-0064-0000-0000-0000037E2149 X-IBM-SpamModules-Scores: X-IBM-SpamModules-Versions: BY=3.00010148; HX=3.00000242; KW=3.00000007; PH=3.00000004; SC=3.00000270; SDB=6.01125006; UDB=6.00584144; IPR=6.00905133; MB=3.00024399; MTD=3.00000008; XFM=3.00000015; UTC=2018-11-30 16:29:01 X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 18113016-0065-0000-0000-00003B837D1B Message-Id: <092f6c45ed027f87bd7e363764a0ac59@linux.vnet.ibm.com> X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-11-30_07:, , signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=998 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1811300140 X-BeenThere: openbmc@lists.ozlabs.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Development list for OpenBMC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Nov 2018 16:29:07 -0000 The OpenBMC Security Working group is working toward becoming a CVE Numbering Authority (CNA)[1] as the way to share security vulnerabilities. Our draft application is in Gerrit review 15621[2]. It talks about the exact boundary between OpenBMC and closely related code such as Yocto, OpenEmbedded, and support for various machines and boards. It also addresses how to handle forked versions of OpenBMC. I am seeking input especially in these areas. This initiative is an add-on piece that would be handled by the "OpenBMC security vulnerability reporting process"[3]. Please review. Thanks, Joseph [1]: https://cve.mitre.org/cve/ "CVE / CNA" [2]: https://gerrit.openbmc-project.xyz/#/c/15621 "draft CNA application" then click on cna-request.md [3]: https://github.com/openbmc/docs/blob/master/security/obmc-security-response-team.md "OpenBMC security vulnerability reporting process"