Date: Wed, 20 Feb 2013 09:03:38 -0500 From: Eitan Adler <eadler@freebsd.org> To: Alexey Dokuchaev <danfe@freebsd.org> Cc: svn-ports-head@freebsd.org, svn-ports-all@freebsd.org, Ruslan Mahmatkhanov <rm@freebsd.org>, ports-committers@freebsd.org Subject: Re: svn commit: r312626 - head/security/vuxml Message-ID: <CAF6rxg=AAEcuPzS_Hoeu%2B1KcpPeSxQxyW0czAM7BYiQgJ1KfTA@mail.gmail.com> In-Reply-To: <20130220140104.GA75978@FreeBSD.org> References: <201302201358.r1KDwKxc094476@svn.freebsd.org> <20130220140104.GA75978@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 20 February 2013 09:01, Alexey Dokuchaev <danfe@freebsd.org> wrote: > On Wed, Feb 20, 2013 at 01:58:20PM +0000, Ruslan Mahmatkhanov wrote: >> New Revision: 312626 >> URL: http://svnweb.freebsd.org/changeset/ports/312626 >> >> Log: >> - add an entry for net/nss-pam-ldapd stack-based buffer overflow >> >> According to advisory, vulnerability exists in nss-pam-ldapd < 0.8.11, >> but since we never had this version in the ports tree, mark everything >> < 0.8.12 as vulnerable. > > This seems weird. Is there any limitation in VuXML that we need to cope > with by introducing such inconsistencies with official advisories? VuXML is intended to address FreeBSD user concerns, not upstream concerns. There isn't a limitation here, but it makes sense to write the VuXML <range> this way. -- Eitan Adler Source, Ports, Doc committer Bugmeister, Ports Security teams
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAF6rxg=AAEcuPzS_Hoeu%2B1KcpPeSxQxyW0czAM7BYiQgJ1KfTA>