Date: Sat, 12 Aug 2006 13:20:25 +0200 From: "Simon L. Nielsen" <simon@FreeBSD.org> To: Adrian Penisoara <ady@freebsd.ady.ro> Cc: freebsd-isp@freebsd.org, freebsd-security@freebsd.org Subject: Re: Ports security [was: Ports/source dance] Message-ID: <20060812112024.GA1076@zaphod.nitro.dk> In-Reply-To: <9e01a0da0608110010nb48e90fra21f149b836d32fa@mail.gmail.com> References: <20060810132435.GB2636@rabbit> <44DB9955.10102@FreeBSD.org> <20060810204943.GG2164@rabbit> <9e01a0da0608110010nb48e90fra21f149b836d32fa@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2006.08.11 10:10:19 +0300, Adrian Penisoara wrote: > On 8/10/06, Mark Bucciarelli <mark@gaiahost.coop> wrote: > > > >There's a scary security alert from yesterday out and no port > >update so I judged it to be isp-related. I looked for > >ports-security list but didn't see one. > > You know, that might be a very good ideea -- e.g. have a security team and > list for ports as we have one for the base distribution. There should be > enough volunteers. > > What would the FreeBSD security officer say about this ? I was not on freebsd-isp, so I hadn't seen the start of this thread. Ports security issues should go to either freebsd-ports@, freebsd-security@, or directly to the FreeBSD Security Team at secteam@FreeBSD.org, if you want to catch the attention of the Security Team. I don't currently see enough volume with regards to ports security issues to warrant a separate mailing list. I think using freebsd-security@ should be fine, and we can always create a new list if needed. With regards to a separate security team for ports, it has been discussed in the past, but so far hasn't been created mainly since it haven't been a problem for secteam members working on ports just being part of the "normal" secteam, while only/mostly working on ports issues. It would be very nice if more people helped out with the ports side of FreeBSD security, but when we had the last call for volunteers among committers there weren't a lot of people volunteering to help out with ports as part of the Security Team. That said, it's certainly no requirement to be a committer or to be part of secteam to help out. Just create VuXML entries [1] [2] and send them to freebsd-vuxml@FreeBSD.org or secteam@FreeBSD.org for review and commit, or fix issues and send patches as PR's where secteam is CC'ed. -- Simon L. Nielsen FreeBSD Deputy Security Officer
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060812112024.GA1076>