From owner-svn-ports-all@FreeBSD.ORG Wed Sep 12 13:27:00 2012 Return-Path: Delivered-To: svn-ports-all@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 1033) id 20CEF106566C; Wed, 12 Sep 2012 13:27:00 +0000 (UTC) Date: Wed, 12 Sep 2012 13:27:00 +0000 From: Alexey Dokuchaev To: Eitan Adler Message-ID: <20120912132700.GA6185@FreeBSD.org> References: <201209120731.q8C7VMJ4020038@svn.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Cc: svn-ports-head@freebsd.org, svn-ports-all@freebsd.org, ports-committers@freebsd.org Subject: Re: svn commit: r304136 - head/security/vuxml X-BeenThere: svn-ports-all@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SVN commit messages for the ports tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Sep 2012 13:27:00 -0000 On Wed, Sep 12, 2012 at 08:48:31AM -0400, Eitan Adler wrote: > On 12 September 2012 03:31, Alexey Dokuchaev wrote: > > Author: danfe > > Date: Wed Sep 12 07:31:22 2012 > > New Revision: 304136 > > URL: http://svn.freebsd.org/changeset/ports/304136 > > > > Log: > > Update NVIDIA arbitrary memory access vulnerability with CVE-2012-4225. > > Thank you for working to document this issue. Since the vulnerability > is separate issue and could you please create a new VuXML entry > instead? I thought about it, but then after studying the patch, got convinced that actually the issue is the same, but first patch did not address is completely. Do you have another considerations that would warrant separate entry? ./danfe