Re: FreeBSD Security Advisory FreeBSD-SA-21:08.vm missing in vuxml

2021-04-13 Thread Gian Piero Carrubba
* [Mon, Apr 12, 2021 at 09:03:08PM -0700] Gordon Tetlow via freebsd-security: The current issues were committed to vuxml 6 days ago. Apparently, the backend that serves the vuxml for clients hasn’t been updated for the ports git transition. There is a pr for that already and hopefully it will

Re: FreeBSD Security Advisory FreeBSD-SA-21:08.vm missing in vuxml

2021-04-13 Thread Miroslav Lachman
On 13/04/2021 06:03, Gordon Tetlow wrote: On Apr 12, 2021, at 03:21, Miroslav Lachman <000.f...@quip.cz> wrote: On 11/04/2021 21:49, Gian Piero Carrubba wrote: * [Sun, Apr 11, 2021 at 09:36:05PM +0200] Miroslav Lachman: On 11/04/2021 21:21, Gian Piero Carrubba wrote: CCing ports-secteam@ a

Re: FreeBSD Security Advisory FreeBSD-SA-21:08.vm missing in vuxml

2021-04-12 Thread Gordon Tetlow via freebsd-security
> On Apr 12, 2021, at 03:21, Miroslav Lachman <000.f...@quip.cz> wrote: > > On 11/04/2021 21:49, Gian Piero Carrubba wrote: >> * [Sun, Apr 11, 2021 at 09:36:05PM +0200] Miroslav Lachman: On 11/04/2021 21:21, Gian Piero Carrubba wrote: > CCing ports-secteam@ as it seems a more appropriat

Re: FreeBSD Security Advisory FreeBSD-SA-21:08.vm missing in vuxml

2021-04-12 Thread Miroslav Lachman
On 11/04/2021 21:49, Gian Piero Carrubba wrote: * [Sun, Apr 11, 2021 at 09:36:05PM +0200] Miroslav Lachman: On 11/04/2021 21:21, Gian Piero Carrubba wrote: CCing ports-secteam@ as it seems a more appropriate recipient. Vulnerabilities in base should be handled by core secteam, not ports sect