From owner-freebsd-ports@freebsd.org Sat Dec 22 11:42:32 2018 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 7CCCE135079E; Sat, 22 Dec 2018 11:42:32 +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 1936D8539F; Sat, 22 Dec 2018 11:42:30 +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 8A30A38DA4; Sat, 22 Dec 2018 03:42:29 -0800 (PST) Received: from [IPv6:fe80::dd2a:ba9e:2d4a:7c5f] (unknown [IPv6:fe80::dd2a:ba9e:2d4a:7c5f]) by chombo.houseloki.net (Postfix) with ESMTPSA id 4828C1AC9; Sat, 22 Dec 2018 03:42:28 -0800 (PST) Subject: Re: Bug 233749 - net/samba47, net/samba48: Merge ports r486043 to 2018Q4 (Fixes several vulnerabilities) From: Mel Pilgrim To: FreeBSD Ports ML Cc: ports-secteam@FreeBSD.org, "Timur I. Bakeyev" , portmgr@freebsd.org References: <1b5e5e0a-f492-5ec0-a70c-dc34d1d26c01@bluerosetech.com> Message-ID: Date: Sat, 22 Dec 2018 03:42:26 -0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.3.3 MIME-Version: 1.0 In-Reply-To: <1b5e5e0a-f492-5ec0-a70c-dc34d1d26c01@bluerosetech.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 1936D8539F 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.98 / 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)[]; RCPT_COUNT_THREE(0.00)[4]; R_SPF_ALLOW(-0.20)[+mx]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[bluerosetech.com]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; TO_DN_SOME(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; IP_SCORE(-0.80)[asn: 36236(-3.91), country: US(-0.08)]; MX_GOOD(-0.01)[echo.brtsvcs.net,foxtrot.brtsvcs.net]; NEURAL_HAM_SHORT(-0.87)[-0.871,0]; 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: Sat, 22 Dec 2018 11:42:32 -0000 On 2018-12-12 19:19, Mel Pilgrim wrote: > Would someone work on ports/233749, please?  The original security fix > was committed to head 15 days ago, but has yet to be merged to quarterly. I realize it's the holidays, but this is a security fix for a major port. Or is it the plan to let this go unfixed in 2018Q4?