Return-Path: Authentication-Results: lists.ozlabs.org; spf=pass (sender SPF authorized) smtp.mailfrom=linux.ibm.com (client-ip=148.163.156.1; helo=mx0a-001b2d01.pphosted.com; envelope-from=jrey@linux.ibm.com; receiver=) Authentication-Results: lists.ozlabs.org; dmarc=none (p=none dis=none) header.from=linux.ibm.com Received: from mx0a-001b2d01.pphosted.com (mx0a-001b2d01.pphosted.com [148.163.156.1]) (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 49CmbX5RvtzDr7V for ; Fri, 1 May 2020 06:06:00 +1000 (AEST) Received: from pps.filterd (m0098399.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.16.0.42/8.16.0.42) with SMTP id 03UK2jF3082909 for ; Thu, 30 Apr 2020 16:05:58 -0400 Received: from ppma01dal.us.ibm.com (83.d6.3fa9.ip4.static.sl-reverse.com [169.63.214.131]) by mx0a-001b2d01.pphosted.com with ESMTP id 30mhc41gtp-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for ; Thu, 30 Apr 2020 16:05:58 -0400 Received: from pps.filterd (ppma01dal.us.ibm.com [127.0.0.1]) by ppma01dal.us.ibm.com (8.16.0.27/8.16.0.27) with SMTP id 03UK5MbS012734 for ; Thu, 30 Apr 2020 20:05:57 GMT Received: from b03cxnp08025.gho.boulder.ibm.com (b03cxnp08025.gho.boulder.ibm.com [9.17.130.17]) by ppma01dal.us.ibm.com with ESMTP id 30mcu7m5ve-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for ; Thu, 30 Apr 2020 20:05:57 +0000 Received: from b03ledav001.gho.boulder.ibm.com (b03ledav001.gho.boulder.ibm.com [9.17.130.232]) by b03cxnp08025.gho.boulder.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id 03UK5tWR28115262 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Thu, 30 Apr 2020 20:05:55 GMT Received: from b03ledav001.gho.boulder.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 260DF6E059 for ; Thu, 30 Apr 2020 20:05:56 +0000 (GMT) Received: from b03ledav001.gho.boulder.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id DD1A36E04E for ; Thu, 30 Apr 2020 20:05:55 +0000 (GMT) Received: from demeter.roc.mn.charter.com (unknown [9.85.137.230]) by b03ledav001.gho.boulder.ibm.com (Postfix) with ESMTPS for ; Thu, 30 Apr 2020 20:05:55 +0000 (GMT) Subject: Re: Security Working Group - Wednesday April 29 - results From: Joseph Reynolds To: openbmc References: Message-ID: Date: Thu, 30 Apr 2020 15:05:54 -0500 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:68.0) Gecko/20100101 Thunderbird/68.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-TM-AS-GCONF: 00 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.138, 18.0.676 definitions=2020-04-30_12:2020-04-30, 2020-04-30 signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 suspectscore=0 impostorscore=0 priorityscore=1501 adultscore=0 lowpriorityscore=0 spamscore=0 bulkscore=0 mlxlogscore=999 phishscore=0 mlxscore=0 malwarescore=0 clxscore=1015 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2003020000 definitions=main-2004300147 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: Thu, 30 Apr 2020 20:06:01 -0000 On 4/28/20 11:12 AM, Joseph Reynolds wrote: > This is a reminder of the OpenBMC Security Working Group meeting > scheduled for this Wednesday April 29 at 10:00am PDT. > > We'll discuss current development items, and anything else that comes up. > > The current topics: > > 1. Skip May 13 meeting due to OCP Summit? We'll decide later. > > 2. IPMI over DTLS. See discussion happening in the email list. > > 3. Requirements for security audit logs.  Access, deleting, APIs. There was general support for the ideas that the BMC should have dedicated security audit log that could not be deleted or cleared. This log would have only security-relevant events. > > 4. Using mTLS for HTTPS access to BMCWeb. TODO: Joseph to ask for docs from the developers who created the patch. > > 5. Rate-limit BMCWeb authentication failures. The concept was favorably received, with lots of questions about details. TODO: Joseph will push a BMCWeb patch with a proof of concept. > > 6. Review Dropbear (SSH server) settings. Yep. > > 7. OWASP dependency checker. See next item. Item 8 added during the meeting: 8. How do we run dynamic scan tools that are privately licensed and the output of which is copyrighted which means it cannot be shared with the OpenBMC community? We shared our current practices which does allow pushing the fixes back into the project.  TODO: Joseph will document this practice and add it to the security working group wiki. The we discussed if we can use tools because we are a Linux function project.   TODO: Joseph to followup with Kurt. - Joseph > > > Access, agenda, and notes are in the wiki: > > https://github.com/openbmc/openbmc/wiki/Security-working-group > > - Joseph