From owner-freebsd-security@FreeBSD.ORG  Wed Aug  8 13:08:17 2012
Return-Path: <owner-freebsd-security@FreeBSD.ORG>
Delivered-To: freebsd-security@freebsd.org
Received: by hub.freebsd.org (Postfix, from userid 1033)
	id 644CC106566C; Wed,  8 Aug 2012 13:08:17 +0000 (UTC)
Date: Wed, 8 Aug 2012 13:08:17 +0000
From: Alexey Dokuchaev <danfe@FreeBSD.org>
To: Wesley Shields <wxs@FreeBSD.org>
Message-ID: <20120808130817.GA86124@FreeBSD.org>
References: <CAPjTQNHv9CiLYu-r3OHHZfF1HhHYL7yuiefjOD8BqZm8hi3o=Q@mail.gmail.com>
	<501F7A35.5080207@FreeBSD.org> <501FAF5E.6090101@gwdg.de>
	<20120808103406.GA56960@FreeBSD.org>
	<20120808123843.GA31238@atarininja.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=koi8-r
Content-Disposition: inline
In-Reply-To: <20120808123843.GA31238@atarininja.org>
User-Agent: Mutt/1.4.2.1i
X-Mailman-Approved-At: Wed, 08 Aug 2012 13:14:58 +0000
Cc: Doug Barton <dougb@FreeBSD.org>,
	freebsd security <freebsd-security@freebsd.org>,
	Rainer Hurling <rhurlin@gwdg.de>, freebsd-ports@FreeBSD.org,
	Oliver Pinter <oliver.pntr@gmail.com>
Subject: Re: [Full-disclosure] nvidia linux binary driver priv escalation
	exploit
X-BeenThere: freebsd-security@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "Security issues \[members-only posting\]"
	<freebsd-security.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-security>, 
	<mailto:freebsd-security-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-security>
List-Post: <mailto:freebsd-security@freebsd.org>
List-Help: <mailto:freebsd-security-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-security>, 
	<mailto:freebsd-security-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Aug 2012 13:08:17 -0000

On Wed, Aug 08, 2012 at 08:38:43AM -0400, Wesley Shields wrote:
> On Wed, Aug 08, 2012 at 10:34:06AM +0000, Alexey Dokuchaev wrote:
> > VuXML entry will have to follow separately, as it is unclear whether new
> > CVE number will be assigned or not.
> 
> You can do the VuXML without a CVE for now and update it when/if one is
> assigned.

True...  I will commit VuXML together with legacy drivers update.

./danfe