Re: FreeBSD Security Advisory FreeBSD-SA-21:08.vm

2021-04-11 Thread Gian Piero Carrubba
* [Tue, Apr 06, 2021 at 08:22:58PM +] FreeBSD Security Advisories: FreeBSD-SA-21:08.vm Security * [Tue, Apr 06, 2021 at 08:23:03PM +] FreeBSD Security Advisories: FreeBSD-SA-21:09.accept_filter Security * [Tue, Apr

Re: FreeBSD Security Advisory FreeBSD-SA-21:08.vm

2021-04-11 Thread Gian Piero Carrubba
CCing ports-secteam@ as it seems a more appropriate recipient. * [Sun, Apr 11, 2021 at 09:58:24AM +0200] Gian Piero Carrubba: * [Tue, Apr 06, 2021 at 08:22:58PM +] FreeBSD Security Advisories: FreeBSD-SA-21:08.vm Security * [Tue, Apr 06, 2021 at 08

Re: FreeBSD Security Advisory FreeBSD-SA-21:08.vm

2021-04-11 Thread Gian Piero Carrubba
* [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 secteam. The maintainer address for vuxml is ports

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