Date: Sun, 11 Apr 2021 21:36:05 +0200 From: Miroslav Lachman <000.fbsd@quip.cz> To: freebsd-security@freebsd.org Subject: Re: FreeBSD Security Advisory FreeBSD-SA-21:08.vm Message-ID: <ab68d1d4-5ba3-3e94-b381-3b6d86516796@quip.cz> In-Reply-To: <20210411192125.knknarbiul3alggx@robinhood.fdc.rm-rf.it> References: <20210406202258.1642E15C4A@freefall.freebsd.org> <20210406202303.3B6F715D1E@freefall.freebsd.org> <20210406202309.EECD015EA7@freefall.freebsd.org> <20210411075824.fzrbnrtus6iiw2cq@robinhood.fdc.rm-rf.it> <20210411192125.knknarbiul3alggx@robinhood.fdc.rm-rf.it>
next in thread | previous in thread | raw e-mail | index | archive | help
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. Vuxml entries should be published together with Security Advisories. Miroslav Lachman > * [Sun, Apr 11, 2021 at 09:58:24AM +0200] Gian Piero Carrubba: >> * [Tue, Apr 06, 2021 at 08:22:58PM +0000] FreeBSD Security Advisories: >>> FreeBSD-SA-21:08.vm Security >> >> * [Tue, Apr 06, 2021 at 08:23:03PM +0000] FreeBSD Security Advisories: >>> FreeBSD-SA-21:09.accept_filter Security >> >> * [Tue, Apr 06, 2021 at 08:23:09PM +0000] FreeBSD Security Advisories: >>> FreeBSD-SA-21:10.jail_mount Security >> >> Not sure if this is the correct list for notifying about it, but none >> of the above mentioned SAs has been included in >> https://svn.freebsd.org/ports/head/security/vuxml/vuln.xml. This is a >> bit of inconvenience for people using base-audit like me. >> More in general, which is the right process for including new SAs into >> vuln.xml? >> >> Thanks, >> Gian Piero.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ab68d1d4-5ba3-3e94-b381-3b6d86516796>