Date: Wed, 27 Jun 2012 15:35:51 -0400 From: Wesley Shields <wxs@FreeBSD.org> To: Ryan Steinmetz <zi@FreeBSD.org> Cc: cvs-ports@FreeBSD.org, cvs-all@FreeBSD.org, ports-committers@FreeBSD.org Subject: Re: cvs commit: ports/security/vuxml vuln.xml Message-ID: <20120627193551.GB89288@atarininja.org> In-Reply-To: <201206271534.q5RFYiqv033640@repoman.freebsd.org> References: <201206271534.q5RFYiqv033640@repoman.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jun 27, 2012 at 03:34:44PM +0000, Ryan Steinmetz wrote: > zi 2012-06-27 15:34:44 UTC > > FreeBSD ports repository > > Modified files: > security/vuxml vuln.xml > Log: > - Document recent FreeBSD SA's for 2012: SA-12:04.sysret, > SA-12:03.bind, SA-12:02.crypt, SA-12:01.openssl > > Reviewed by: wxs Thanks! I had been meaning to do this but keep running out of time to do it. It would be nice if these were prepared by someone(TM) and committed along with the fixes. Getting these out to portaudit users is a useful thing to do. I don't want to add on to secteam's work but I do want to at least bring it up as something we should formalize for SAs. Before anyone asks: yes, if I knew about SAs going out ahead of time I would make sure I prepare the updates to go in time. It's just so annoying to do after-the-fact that I kept putting it off. -- WXS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120627193551.GB89288>