Date: Thu, 5 Apr 2018 13:34:38 -0700 From: Mel Pilgrim <list_freebsd@bluerosetech.com> To: Thomas Zander <riggs@freebsd.org> Cc: Freebsd Ports <freebsd-ports@freebsd.org> Subject: Re: How to get timely MFH of security commits? Message-ID: <80e55f31-f6d0-b8a7-c959-95e25f9b96b7@bluerosetech.com> In-Reply-To: <CAFU734xaayYTWoPhp0i4O4iuBmkvJA4iPh9aMzRwTds=%2BqAMzQ@mail.gmail.com> References: <3757bd87-a536-c3ae-ef71-1a68fe6c3e45@bluerosetech.com> <CAFU734zUTexr=UowMkF1u6U8ba-t5=1LF5C0Q0rWwX1RzziiGQ@mail.gmail.com> <b5723cc4-5bdc-6825-5b33-a3e9e83b5fce@bluerosetech.com> <CAFU734xaayYTWoPhp0i4O4iuBmkvJA4iPh9aMzRwTds=%2BqAMzQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2018-04-05 12:48, Thomas Zander wrote: > Hi, > > On 4 April 2018 at 11:30, Mel Pilgrim <list_freebsd@bluerosetech.com> wrote: > >> On the topic of MFH emails, were those for r453380 and r465710 (both >> security updates to security/openssl with MFH tags) not sent? > > Those mails were sent on March 27th and should have been addressed, sorry. The one for r465710 would have been sent then, but r453380 happened on 2 November 2017 and wasn't addressed until bug 223797 was opened on 21 Nov. To the security team's credit, though, the bug received quick response. This is getting a bit off track. This thread was more about bring up an observed pattern that is potentially a serious problem, inviting community support, and hoping it will spur the right people to solving what needs solving. Thanks you for your responses.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?80e55f31-f6d0-b8a7-c959-95e25f9b96b7>