From owner-freebsd-announce@freebsd.org Tue Jun 9 16:58:25 2020 Return-Path: Delivered-To: freebsd-announce@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 38EDC332A3D for ; Tue, 9 Jun 2020 16:58:25 +0000 (UTC) (envelope-from security-advisories@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49hGXd0mrrz44Kw; Tue, 9 Jun 2020 16:58:25 +0000 (UTC) (envelope-from security-advisories@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 945) id 08ACE149EA; Tue, 9 Jun 2020 16:58:25 +0000 (UTC) From: FreeBSD Errata Notices To: FreeBSD Errata Notices Reply-To: freebsd-stable@freebsd.org Precedence: bulk Message-Id: <20200609165825.08ACE149EA@freefall.freebsd.org> Date: Tue, 9 Jun 2020 16:58:25 +0000 (UTC) Subject: [FreeBSD-Announce] FreeBSD Errata Notice FreeBSD-EN-20:11.ena X-BeenThere: freebsd-announce@freebsd.org X-Mailman-Version: 2.1.33 List-Id: "Project Announcements \[moderated\]" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Jun 2020 16:58:25 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 ============================================================================= FreeBSD-EN-20:11.ena Errata Notice The FreeBSD Project Topic: Stability issues in ena(4) driver Category: core Module: ena Announced: 2020-06-09 Credits: Colin Percival Affects: FreeBSD 12.1 Corrected: 2020-05-12 18:44:41 UTC (stable/12, 12.1-STABLE) 2020-06-09 16:10:57 UTC (releng/12.1, 12.1-RELEASE-p6) For general information regarding FreeBSD Errata Notices and Security Advisories, including descriptions of the fields above, security branches, and the following sections, please visit . I. Background The ena(4) driver is used to access the Elastic Network Adapter network interface on recent Amazon Elastic Compute Cloud (EC2) instances. It is designed to make full use of the EC2 network, operating at up to 100 Gbps. II. Problem Description The ena(4) driver attempts to allocate a large number of 16 kB mbuf clusters to use as buffers for received packets. Under low memory conditions, the process of attempting to allocate these buffers may take a long time. On FreeBSD 12.x, these allocations are attempted from an interrupt thread running at high priority, and can subsequently starve other parts of the system of CPU time. It appears that systems using the ZFS filesystem may be more likely to experience this issue, possibly due to the memory pressure created by the allocation of memory to the ZFS ARC. III. Impact The system may become unresponsive, appearing to "lock up" for periods of several seconds. The ena(4) driver may log errors such as The number of lost tx completion is above the threshold (129 > 128). and reset the device; the nvme(4) driver may also experience timeouts resulting in a range of errors being reported and the device being reset, and in some cases causing kernel panics. IV. Workaround No workaround is available. Systems which are not part of the Amazon Elastic Compute Cloud (EC2) are not affected; nor are older EC2 instance types, which lack the Elastic Network Adapter hardware. V. Solution Upgrade your system to a supported FreeBSD stable or release / security branch (releng) dated after the correction date, and reboot. Perform one of the following: 1) To update your system via a binary patch: Systems running a RELEASE version of FreeBSD on the i386 or amd64 platforms can be updated via the freebsd-update(8) utility: # freebsd-update fetch # freebsd-update install # shutdown -r +10min "Rebooting for errata update" 2) To update your system via a source code patch: The following patches have been verified to apply to the applicable FreeBSD release branches. a) Download the relevant patch from the location below, and verify the detached PGP signature using your PGP utility. [FreeBSD 12.1] # fetch https://security.FreeBSD.org/patches/EN-20:11/ena.patch # fetch https://security.FreeBSD.org/patches/EN-20:11/ena.patch.asc # gpg --verify ena.patch.asc b) Apply the patch. Execute the following commands as root: # cd /usr/src # patch < /path/to/patch c) Recompile your kernel as described in and reboot the system. NOTE: This patch can have a small (~2%) impact on the throughput of the ena(4) device. The original performance can be restored -- at the expense of latency spikes and system instability under memory pressure -- by adding the following to /boot/loader.conf: hw.ena.enable_9k_mbufs="1" VI. Correction details The following list contains the correction revision numbers for each affected branch. Branch/path Revision - ------------------------------------------------------------------------- stable/12/ r360985 releng/12.1/ r361970 - ------------------------------------------------------------------------- To see which files were modified by a particular revision, run the following command, replacing NNNNNN with the revision number, on a machine with Subversion installed: # svn diff -cNNNNNN --summarize svn://svn.freebsd.org/base Or visit the following URL, replacing NNNNNN with the revision number: VII. References The latest revision of this advisory is available at -----BEGIN PGP SIGNATURE----- iQKTBAEBCgB9FiEE/A6HiuWv54gCjWNV05eS9J6n5cIFAl7fuERfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEZD MEU4NzhBRTVBRkU3ODgwMjhENjM1NUQzOTc5MkY0OUVBN0U1QzIACgkQ05eS9J6n 5cITew/+MQpJIKHrlWjqcR9fvAeqR4rX3aBVNMkambeTa2nKY4/PH8XzVLnKvyuE O7ZtzaU3bz5xYkyYnlYSGstTRWk/BRCRgpZvzlPWVsvsFINgCHO5QsKHVyC0+/M2 Do3qRwxYDYPh0+Bz8QGuQGmpfMNpsuA//rfa12Ywp7jqu3IP8+0bBuWM71J7Bkyf WhEJIehFiU9iGUFS2LF7000CzIwmcTitCtYJFxxwaYYHGHT5nMtljcrsKK9I1N+Q f3mQ7dK8ryQ+H+CupfHodAYUeZyJbj/xVggdnzY45R1B9Tdr15VMPuurcqXyXIft Uj4UzdDUNgbUw4WQqfvqn8CDAT0V54NRhDs8AkYWn+GqaDDSnvcsKnI/V2UJgqTn Wp8ZClq7bF0mcBp7g1t97peseZsP+papJKsaVLKrTT+dw1x/aWz1cvK51x5UPWoW qaiFVMf5l9R0ZDcQxsyN/7gyHnZRR8X1wl1gVPVcJ8EEWs6Gh4sRTzXSDMDqsA/P 89hA6vPVeOmBqKM3BlR8MrDPIALjzxNvzu65NMLMcebyPudaY9a2GEd8acw6mwxh hQ015y9+MoMV8xD3gfjNLdQS7899eK1MwXu1UZPcUEOlYErAhjoGo51N4D6mfU62 7sDoy2Yt380Nmp57nUoanHkADzXPn8OV8fvlsTN6a0J4ZLu+KNM= =FDu4 -----END PGP SIGNATURE----- From owner-freebsd-announce@freebsd.org Tue Jun 9 16:58:29 2020 Return-Path: Delivered-To: freebsd-announce@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id E6374332A42 for ; Tue, 9 Jun 2020 16:58:29 +0000 (UTC) (envelope-from security-advisories@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49hGXj4Kh7z44Vm; Tue, 9 Jun 2020 16:58:29 +0000 (UTC) (envelope-from security-advisories@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 945) id 81C9314D00; Tue, 9 Jun 2020 16:58:29 +0000 (UTC) From: FreeBSD Errata Notices To: FreeBSD Errata Notices Reply-To: freebsd-stable@freebsd.org Precedence: bulk Message-Id: <20200609165829.81C9314D00@freefall.freebsd.org> Date: Tue, 9 Jun 2020 16:58:29 +0000 (UTC) Subject: [FreeBSD-Announce] FreeBSD Errata Notice FreeBSD-EN-20:12.iflib X-BeenThere: freebsd-announce@freebsd.org X-Mailman-Version: 2.1.33 List-Id: "Project Announcements \[moderated\]" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Jun 2020 16:58:30 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 ============================================================================= FreeBSD-EN-20:12.iflib Errata Notice The FreeBSD Project Topic: iflib watchdog timeout resetting idle queues Category: core Module: kernel Announced: 2020-06-09 Affects: FreeBSD 12.1 Corrected: 2020-01-10 18:29:05 UTC (stable/12, 12.1-STABLE) 2020-06-09 16:11:54 UTC (releng/12.1, 12.1-RELEASE-p6) For general information regarding FreeBSD Errata Notices and Security Advisories, including descriptions of the fields above, security branches, and the following sections, please visit . I. Background iflib is a framework that contains common code for network drivers to use, reducing code duplication. One function it contains is a "watchdog" that periodically checks the driver's software Tx queues to see if they're hung. II. Problem Description The iflib watchdog would sometimes trigger a false positive queue hang just after a link state change. III. Impact The iflib framework would print messages for the affected devices such as "igb0: TX(2) desc avail = 1024, pidx = 0" and would stop allowing Tx traffic to be sent. IV. Workaround No workaround is available. Systems that do not use iflib-based interfaces are not vulnerable. V. Solution Upgrade your system to a supported FreeBSD stable or release / security branch (releng) dated after the correction date, and reboot. Perform one of the following: 1) To update your system via a binary patch: Systems running a RELEASE version of FreeBSD on the i386 or amd64 platforms can be updated via the freebsd-update(8) utility: # freebsd-update fetch # freebsd-update install # shutdown -r +10min "Rebooting for errata update" 2) To update your system via a source code patch: The following patches have been verified to apply to the applicable FreeBSD release branches. a) Download the relevant patch from the location below, and verify the detached PGP signature using your PGP utility. # fetch https://security.FreeBSD.org/patches/EN-20:12/iflib.patch # fetch https://security.FreeBSD.org/patches/EN-20:12/iflib.patch.asc # gpg --verify iflib.patch.asc b) Apply the patch. Execute the following commands as root: # cd /usr/src # patch < /path/to/patch c) Recompile your kernel as described in and reboot the system. VI. Correction details The following list contains the correction revision numbers for each affected branch. Branch/path Revision - ------------------------------------------------------------------------- stable/12/ r356605 releng/12.1/ r361971 - ------------------------------------------------------------------------- To see which files were modified by a particular revision, run the following command, replacing NNNNNN with the revision number, on a machine with Subversion installed: # svn diff -cNNNNNN --summarize svn://svn.freebsd.org/base Or visit the following URL, replacing NNNNNN with the revision number: VII. References The latest revision of this advisory is available at -----BEGIN PGP SIGNATURE----- iQKTBAEBCgB9FiEE/A6HiuWv54gCjWNV05eS9J6n5cIFAl7fuQlfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEZD MEU4NzhBRTVBRkU3ODgwMjhENjM1NUQzOTc5MkY0OUVBN0U1QzIACgkQ05eS9J6n 5cJl3RAAhIgmZfpK3r2qBuwC0EypnqtndvjEHGTTdcUhwY0iBjrDxt6AnHPMO/i/ DEZkNJI6uCxSaybjVcnNob7lJ4p2o9rrAF+pExR4LycxJa0y8oZM5xIdqwwfY484 Tge4/N4garWeA0ALetGXCrAf62t7ZLRgyWldH4tt4m0Mu7AIGkfPGivWK6kpmB5c O/GKv6fe4TiyPSAQroUQrNawdO9tQTDhXjGknRZ3iyu9tp/zeOkgtMAEnc3zdv0T J3sFqGGt/Mt2dL0KoqfUNK54k5vgUU+oV22+z2pf9TGtby4yUq0FTOxl+V5qE6hk aQHndYgklOo56AaSkA3GW1DoIOyU7VQtsA5hpbHXotiJo1P5BoNIa3IwMfLBmW45 sD7f/vpyX5Mga9KqcvYIgRxCNvYpu8Dq0nKiVQboABAdplFLorTdHPJmSqmeoomO diEQk3cSotrav1b8xl2IfZYk8TaC5B7gm9UuU6ag6UM/vasr1kRcz5+7DxDOCP1d 2CbaKqPnpGAxyGmd+DLO7EMkOIBPiKfoCtBfgLXRypD6ypEW/xAUmGtR6yIFCtJ/ USAHRwrm0jteVOXYrpS3cvBYsXkEowcMK1n8ghIqUfDHtvebLK2m5ubhF2E1F0Gv 6Nw6i0dt1Csrhg7CyrWqzY83iB7N3tPvqN45QaFMEBRqnnsLPpQ= =VqeW -----END PGP SIGNATURE----- From owner-freebsd-announce@freebsd.org Tue Jun 9 16:58:42 2020 Return-Path: Delivered-To: freebsd-announce@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 18106332AEA for ; Tue, 9 Jun 2020 16:58:42 +0000 (UTC) (envelope-from security-advisories@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49hGXx6RD1z44WR; Tue, 9 Jun 2020 16:58:41 +0000 (UTC) (envelope-from security-advisories@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 945) id CCF2014A7B; Tue, 9 Jun 2020 16:58:41 +0000 (UTC) From: FreeBSD Security Advisories To: FreeBSD Security Advisories Reply-To: freebsd-security@freebsd.org Precedence: bulk Message-Id: <20200609165841.CCF2014A7B@freefall.freebsd.org> Date: Tue, 9 Jun 2020 16:58:41 +0000 (UTC) Subject: [FreeBSD-Announce] FreeBSD Security Advisory FreeBSD-SA-20:17.usb X-BeenThere: freebsd-announce@freebsd.org X-Mailman-Version: 2.1.33 List-Id: "Project Announcements \[moderated\]" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Jun 2020 16:58:42 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 ============================================================================= FreeBSD-SA-20:17.usb Security Advisory The FreeBSD Project Topic: USB HID descriptor parsing error Category: core Module: kernel Announced: 2020-06-09 Credits: Andy Nguyen, Google Affects: All supported versions of FreeBSD. Corrected: 2020-06-08 09:32:57 UTC (stable/12, 12.1-STABLE) 2020-06-09 16:13:54 UTC (releng/12.1, 12.1-RELEASE-p6) 2020-06-08 09:33:37 UTC (stable/11, 11.4-STABLE) 2020-06-09 16:13:54 UTC (releng/11.4, 11.4-RC2-p1) 2020-06-09 16:13:54 UTC (releng/11.3, 11.3-RELEASE-p10) CVE Name: CVE-2020-7456 For general information regarding FreeBSD Security Advisories, including descriptions of the fields above, security branches, and the following sections, please visit . I. Background USB Human Interface Device (HID) descriptors may push/pop the current state to allow description of items residing in a so-called union. FreeBSD supports 4 such pop levels. II. Problem Description If the push/pop level is not restored within the processing of the same HID item, an invalid memory location may be used for subsequent HID item processing. III. Impact An attacker with physical access to a USB port may be able to use a specially crafted USB device to gain kernel or user-space code execution. IV. Workaround Setting "sysctl hw.usb.disable_enumeration=1" disables USB device enumeration preventing the error from occurring. V. Solution Upgrade your vulnerable system to a supported FreeBSD stable or release / security branch (releng) dated after the correction date, and reboot. Perform one of the following: 1) To update your vulnerable system via a binary patch: Systems running a RELEASE version of FreeBSD on the i386 or amd64 platforms can be updated via the freebsd-update(8) utility: # freebsd-update fetch # freebsd-update install # shutdown -r +10min "Rebooting for a security update" 2) To update your vulnerable system via a source code patch: The following patches have been verified to apply to the applicable FreeBSD release branches. a) Download the relevant patch from the location below, and verify the detached PGP signature using your PGP utility. # fetch https://security.FreeBSD.org/patches/SA-20:17/usb.patch # fetch https://security.FreeBSD.org/patches/SA-20:17/usb.patch.asc # gpg --verify usb.patch.asc b) Apply the patch. Execute the following commands as root: # cd /usr/src # patch < /path/to/patch c) Recompile your kernel as described in and reboot the system. VI. Correction details The following list contains the correction revision numbers for each affected branch. Branch/path Revision - ------------------------------------------------------------------------- stable/12/ r361918 releng/12.1/ r361972 stable/11/ r361919 releng/11.4/ r361972 releng/11.3/ r361972 - ------------------------------------------------------------------------- To see which files were modified by a particular revision, run the following command, replacing NNNNNN with the revision number, on a machine with Subversion installed: # svn diff -cNNNNNN --summarize svn://svn.freebsd.org/base Or visit the following URL, replacing NNNNNN with the revision number: VII. References The latest revision of this advisory is available at -----BEGIN PGP SIGNATURE----- iQKTBAEBCgB9FiEE/A6HiuWv54gCjWNV05eS9J6n5cIFAl7fuFhfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEZD MEU4NzhBRTVBRkU3ODgwMjhENjM1NUQzOTc5MkY0OUVBN0U1QzIACgkQ05eS9J6n 5cJ4Iw/6AuTNBD33WaEZTW7mAfigc1sp8cjnKCvm+DObx1CNpSr9fxiy+Dy5DMjg /Hv4ijv4flte3txXohdXvYcAKqYrbP1BBr6ptlQYE/V+61sTtxV18XGnID1fgSOZ WPHGaXMAUNeeVxJSEVJ5rJ+lRo90Rlp/n9pMZlU+tIDFjE0BQ5lJkicg/xgFO9rg tRaeotoXmdNo3HlkMfXnIZ8q5tOQrcsfSZP6DgQWKspinCJTVTr1eQ9p6mHNV7Ip XZGuXNaktYxwNk2oWP2dmk6FAkyldReyi856DurhOldmAxPbY5zh4NfwOuL78pSa draF1up4Vkb/aSQHN1xkaOjlBEmLYHgzND83M9gnE2RdtGVLeerI6Gdd6Pp4D8a2 vPgWZOQfO82lUjSx/B/XHCA0Ztu4uinPuCkrf9vcteg/juJxQRRyFWUfqGbo3qpC U9a1AN9Ojgy0eFDKTo7vWUf34kB1RApEEt3y3XNwwbwDWtKdWMRLJfD4oIhbB6Re URYpBUv5wnkhOq5LR15VJc6jL/DZxqsjByALwtnEdNH6bAYM+6WTmnTYFgUyuvlF n2tZeD5LXM0GLs377edmAeGR7TUd+rFfndEGFKiDXeSNrmb0Ro6E4vvbUwu5PalA kf+suJS0noAH+SPmk0YyxKm12plPxyO2zLFIMRpjWz6v1joH+Qk= =4v1s -----END PGP SIGNATURE----- From owner-freebsd-announce@freebsd.org Tue Jun 9 20:13:28 2020 Return-Path: Delivered-To: freebsd-announce@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 4FE0433B794 for ; Tue, 9 Jun 2020 20:13:28 +0000 (UTC) (envelope-from jrm@ftfl.ca) Received: from mail-qk1-f174.google.com (mail-qk1-f174.google.com [209.85.222.174]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49hLsg189hz4Yx3 for ; Tue, 9 Jun 2020 20:13:26 +0000 (UTC) (envelope-from jrm@ftfl.ca) Received: by mail-qk1-f174.google.com with SMTP id c12so22118342qkk.13 for ; Tue, 09 Jun 2020 13:13:26 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:subject:date:message-id:user-agent :mime-version; bh=7PqEtpJ3vwMAaBaaGHdagwG6HvQvrkreuy4wwa+uLPc=; b=JGP6f/faDUVVvsF5Qdhfkd/q5+5hWWqM4ea+j5Btyqh/KARKFPL1vrq9/C28fl414w zfx9en2T+mI9woYMu0SalCkQ7/NtJj0xTYunkqxpx6LqwGl679aR4m74EGZRK+fbmQ1o CRjp+mNsJCRsuhqVo3yqlgZ0FKY1qcfAVv2SDKUxhhnlqn8lJ4OHn4bvnme+e8dWiViP CmbPXjeaw1WcJPdSP0Eb1O5wGupPZM/PlRBjL7UheIeN2ZrCenHkKcM8Crj7F6xtuXOi 34nLde7/JVAJbbYtScBANQPIVfh552imuaJJ2yo1JzB/Xn0VF+1HZPIT+FUPcqk9qQW/ 8/5w== X-Gm-Message-State: AOAM532TL1cQcXemFYA2gKZeJnhH04qRyqVXiBttLNEOr83eJXALzXFV IVO4/QsYFxrvXYBK+Uk/E9acPKqCj9KPSw== X-Google-Smtp-Source: ABdhPJyfjtW2BectlS0S6LlDDutxUlE7XfaWng0pLGiNdv1d9bBxRucw4ePm/Nytg1UONsAkTr5Jew== X-Received: by 2002:a37:74c:: with SMTP id 73mr29045165qkh.75.1591733604896; Tue, 09 Jun 2020 13:13:24 -0700 (PDT) Received: from phe.ftfl.ca.ftfl.ca (drmons0544w-142-177-158-229.dhcp-dynamic.fibreop.ns.bellaliant.net. [142.177.158.229]) by smtp.gmail.com with ESMTPSA id b12sm1144069qkk.43.2020.06.09.13.13.22 for (version=TLS1_2 cipher=ECDHE-ECDSA-CHACHA20-POLY1305 bits=256/256); Tue, 09 Jun 2020 13:13:22 -0700 (PDT) From: FreeBSD Core Team Secretary To: freebsd-announce@freebsd.org Date: Tue, 09 Jun 2020 17:13:20 -0300 Message-ID: <86v9k0huan.fsf@phe.ftfl.ca> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (berkeley-unix) MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" X-Rspamd-Queue-Id: 49hLsg189hz4Yx3 X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of jrm@ftfl.ca designates 209.85.222.174 as permitted sender) smtp.mailfrom=jrm@ftfl.ca X-Spamd-Result: default: False [-0.21 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_MISSING_CHARSET(2.50)[]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17]; TO_DN_NONE(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; SIGNED_PGP(-2.00)[]; FORGED_SENDER(0.30)[core-secretary@FreeBSD.org,jrm@ftfl.ca]; RECEIVED_SPAMHAUS_PBL(0.00)[142.177.158.229:received]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; FROM_NEQ_ENVFROM(0.00)[core-secretary@FreeBSD.org,jrm@ftfl.ca]; TO_DOM_EQ_FROM_DOM(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.22)[-0.216]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-0.75)[-0.752]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-announce@freebsd.org]; DMARC_NA(0.00)[FreeBSD.org]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_SPAM_SHORT(0.35)[0.354]; RCVD_IN_DNSWL_NONE(0.00)[209.85.222.174:from]; RWL_MAILSPIKE_POSSIBLE(0.00)[209.85.222.174:from]; RCVD_TLS_ALL(0.00)[] X-Mailman-Approved-At: Tue, 09 Jun 2020 20:43:14 +0000 Subject: [FreeBSD-Announce] New FreeBSD code of conduct X-BeenThere: freebsd-announce@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Project Announcements \[moderated\]" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Jun 2020 20:13:28 -0000 --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Dear FreeBSD community, The FreeBSD Project has adopted a new LLVM-derived code of conduct. The new code of conduct can be found at https://www.freebsd.org/internal/code-of-conduct.html BACKGROUND Active FreeBSD developers were invited to complete two surveys related to our Code of Conduct. The first survey, conducted in 2018, told us that: - 94% of developers believe respectful communication in the project is important; 1% disagreed - 89% believe FreeBSD should be welcoming to people of all backgrounds; 2% disagreed - 73% say toxic people should be removed from the Project regardless of their technical contribution; 9% disagreed - 35% were dissatisfied with the code of conduct adopted in 2018, 34% were neutral, and 30% were satisfied. These results indicated that there was sufficient dissatisfaction with the current code of conduct to warrant investigation. After reviewing other open source codes of conduct, the FreeBSD Core Team investigated adopting either an LLVM-derived or a Go-derived code of conduct. A second survey was held at the start of June and had only one question: Which code of conduct should FreeBSD adopt? - An LLVM-derived code of conduct: https://github.com/freebsd/core.10-public-docs/blob/master/CoC/llvm-ba= sed.md - A Go-Derived code of conduct: https://github.com/freebsd/core.10-public-docs/blob/master/CoC/golang-= based.md - Retain the current code of conduct: https://web.archive.org/web/20200108075747/https://www.freebsd.org/int= ernal/code-of-conduct.html RESULTS - 4% favoured keeping the current code of conduct - 33% favoured the Go-derived code of conduct - 63% favoured the LLVM-derived code of conduct. Thus, the Core Team, following the preference of a majority of active FreeBSD developers, adopted the LLVM-derived code of conduct. THANK YOU Thank you to the LLVM and Go communities, and our impassioned members who helped champion this evolution. =2D-=20 FreeBSD Core Team --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQGvBAEBCgCZFiEEnwKDb1DTrVq3WsWIDLQD5OlbluwFAl7f7WBfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDlG MDI4MzZGNTBEM0FENUFCNzVBQzU4ODBDQjQwM0U0RTk1Qjk2RUMbHGNvcmUtc2Vj cmV0YXJ5QGZyZWVic2Qub3JnAAoJEAy0A+TpW5bst3AH/3iZx1GJF4Xj2XoICS0+ JT9uMtjGMq8m4W68jCky0a3DjHwer7wb/5aHufWHaIk44HWLYHLiWBD0z3+dLRIq dT5ysYmgVjUP3KY5vV0zIVQFUb71J967e47j2zRH+/+iB76Kqi/9e7BfXq+4JrL8 Ug/vvkAzibG+GyP8uoM1zkDS9oJ9VhDyewtRty1QNC9sBdSIWrBZGWrjztj6H/58 dfzEUzXZ3I4aF7PuVTKoAg15gCirJnh9n15RkwJhJ1l+7h/8npy0O48UgJ3nl1Pa IOfrmveoTm+JOcBOasOs4bJT6aX1XAy5UFXoDPI2Eqmdv0oh7jtSk1G7+tFHRDHS HsQ= =ATBW -----END PGP SIGNATURE----- --=-=-=--