Date: Tue, 21 Nov 2017 19:50:11 -0800 From: Mel Pilgrim <list_freebsd@bluerosetech.com> To: Robert Simmons <rsimmons0@gmail.com>, freebsd-security@freebsd.org Subject: Re: Why no update of base/ports openssl for recent CVEs? Message-ID: <9ebd9468-7c26-de75-79ea-5a8829399d51@bluerosetech.com> In-Reply-To: <CA%2BQLa9C5WU2B9WA7NCKx0y=Cc57GWeyBzs5hB4zkc8vxv-E8aw@mail.gmail.com> References: <9a41694c-fffb-e58c-5946-abbc99160fb4@bluerosetech.com> <CA%2BQLa9C5WU2B9WA7NCKx0y=Cc57GWeyBzs5hB4zkc8vxv-E8aw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2017-11-21 17:11, Robert Simmons wrote: > I don't have an answer for base, but I think if you just update your ports > tree, you will see the update to 1.0.2m was committed on Nov 2nd (2 weeks > and 5 days ago): > https://svnweb.freebsd.org/ports?view=revision&revision=453380 That explains ports: it was never merged to quarterly. Submitted ports/223797 to ask for MFH to 2017Q4.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9ebd9468-7c26-de75-79ea-5a8829399d51>