From owner-freebsd-security@FreeBSD.ORG  Mon May 18 15:04:41 2015
Return-Path: <owner-freebsd-security@FreeBSD.ORG>
Delivered-To: freebsd-security@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 71068475;
 Mon, 18 May 2015 15:04:41 +0000 (UTC)
Received: from mx5.roble.com (mx5.roble.com [206.40.34.5])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "mx5.roble.com", Issuer "mx5.roble.com" (not verified))
 by mx1.freebsd.org (Postfix) with ESMTPS id 6193C14A8;
 Mon, 18 May 2015 15:04:41 +0000 (UTC)
Date: Mon, 18 May 2015 08:04:40 -0700 (PDT)
From: Roger Marquis <marquis@roble.com>
To: Bryan Drewery <bdrewery@FreeBSD.org>
cc: freebsd-security@freebsd.org, freebsd-pkg@freebsd.org, 
 freebsd-ports@freebsd.org
Subject: Re: pkg audit / vuln.xml failures
In-Reply-To: <5559FA0B.8080005@FreeBSD.org>
References: <20150517210259.C25DF76F@hub.freebsd.org>
 <5559FA0B.8080005@FreeBSD.org>
User-Agent: Alpine 2.11 (BSF 23 2013-08-11)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-BeenThere: freebsd-security@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: "Security issues \[members-only posting\]"
 <freebsd-security.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/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: Mon, 18 May 2015 15:04:41 -0000

> ports-secteam@ owns this file, not secteam@.

Thanks for the pointer Bryan.  I would hope that port vulnerability
emails are forwarded from secteam@ to ports-secteam@, by policy, as the
freebsd.org website is not clear on this.  Either way at least I/we now
know the right address/es.

> The team needs more help.
> Would you like to volunteer to submit vuxml updates? Many contributors,
> and committers, feel the file is not easy to contribute to.

I have been submitting ports vulnerability updates and will continue to
do so (now to ports-secteam@).  If there are any open seats on
ports-secteam I would like to contribute on that level as well.

Still interested in the team's policies and procedures, if those are
online somewhere.

Roger Marquis