From owner-freebsd-ports@freebsd.org Wed Jan 2 00:40:59 2019 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9B1FD142F935 for ; Wed, 2 Jan 2019 00:40:59 +0000 (UTC) (envelope-from list_freebsd@bluerosetech.com) Received: from echo.brtsvcs.net (echo.brtsvcs.net [IPv6:2607:f740:c::4ae]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id EC96D6B6EE for ; Wed, 2 Jan 2019 00:40:57 +0000 (UTC) (envelope-from list_freebsd@bluerosetech.com) Received: from chombo.houseloki.net (c-73-240-250-185.hsd1.or.comcast.net [73.240.250.185]) by echo.brtsvcs.net (Postfix) with ESMTPS id CB1FF38D08 for ; Tue, 1 Jan 2019 16:40:49 -0800 (PST) Received: from [IPv6:fe80::7102:4df8:1f13:5c55] (unknown [IPv6:fe80::7102:4df8:1f13:5c55]) by chombo.houseloki.net (Postfix) with ESMTPSA id 389684A6 for ; Tue, 1 Jan 2019 16:40:48 -0800 (PST) To: Freebsd Ports From: Mel Pilgrim Subject: How can we ensure security fixes get MFH'd to quarterly? Message-ID: <187df4a2-4402-8492-6536-cd6b6cdf07de@bluerosetech.com> Date: Tue, 1 Jan 2019 16:40:50 -0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.3.3 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: EC96D6B6EE X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of list_freebsd@bluerosetech.com designates 2607:f740:c::4ae as permitted sender) smtp.mailfrom=list_freebsd@bluerosetech.com X-Spamd-Result: default: False [-3.09 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-ports@freebsd.org]; DMARC_NA(0.00)[bluerosetech.com]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCVD_COUNT_THREE(0.00)[3]; SUBJECT_ENDS_QUESTION(1.00)[]; TO_DN_ALL(0.00)[]; MX_GOOD(-0.01)[echo.brtsvcs.net,foxtrot.brtsvcs.net]; NEURAL_HAM_SHORT(-0.98)[-0.982,0]; IP_SCORE(-0.80)[asn: 36236(-3.91), country: US(-0.08)]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:36236, ipnet:2607:f740:c::/48, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[]; RECEIVED_SPAMHAUS_PBL(0.00)[185.250.240.73.zen.spamhaus.org : 127.0.0.10] X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jan 2019 00:40:59 -0000 On Nov 27, r486043 was committed to head to fix several vulnerabilities in the Samba 4.7 and 4.8 ports, but it wasn't merged to 2018Q4. A PR was opened, but 2018Q4 sat unfixed until it expired at the end of the year. Filing a PR didn't help. Mentioning the PR on this list didn't help. What can be done to prevent further repetitions of this lapse in the future?