From owner-freebsd-isp@FreeBSD.ORG Mon Aug 7 15:56:27 2006 Return-Path: X-Original-To: freebsd-isp@freebsd.org Delivered-To: freebsd-isp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CE32516A4DD for ; Mon, 7 Aug 2006 15:56:27 +0000 (UTC) (envelope-from stevenb@frii.com) Received: from mail.frii.com (phobos02.frii.net [216.17.128.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 87D7A43D49 for ; Mon, 7 Aug 2006 15:56:27 +0000 (GMT) (envelope-from stevenb@frii.com) Received: from [10.10.0.107] (fw01-e2.ftc.frii.net [216.17.230.105]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.frii.com (FRII) with ESMTP id 075B7A43FE for ; Mon, 7 Aug 2006 09:56:27 -0600 (MDT) Message-ID: <44D762AB.6010502@frii.com> Date: Mon, 07 Aug 2006 09:56:27 -0600 From: "Steven H. Baeighkley" User-Agent: Thunderbird 1.5.0.5 (Windows/20060719) MIME-Version: 1.0 To: freebsd-isp@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: question about front page server extensions on freebsd X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Aug 2006 15:56:27 -0000 I have perused the mailing lists and some google searches but I haven't found an answer to this yet. It would seem that MS has pulled support from frontpage server extensions for UNIX as of June 30, 2006. http://www.rtr.com/fpsupport/index.asp From what I gather rtr was recommended by some users as a potential solution to the FP extensions on FreeBSD question. This article seems to indicate that you can't redistribute binaries already downloaded so we don't seem to be able to get a hold of them anymore. Since fp2000 server extensions won't work with fp2002 extensions it doesn't look like the older sytem will work either. So the question I have is what are people doing to solve this problem now? We have a windows web server, but would like to run everything on freebsd since the rest of our operation runs on it. Are we dead in the water and stuck with our MS solution or is there something else out there that is filling this need? thanks Steve B -- --- Steven H. Baeighkley - Systems Administrator Front Range Internet, Inc. stevenb@frii.com - (970) 212-0756 From owner-freebsd-isp@FreeBSD.ORG Mon Aug 7 16:11:16 2006 Return-Path: X-Original-To: freebsd-isp@freebsd.org Delivered-To: freebsd-isp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9C68016A4DF for ; Mon, 7 Aug 2006 16:11:16 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from pi.codefab.com (pi.codefab.com [199.103.21.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id B11E743D53 for ; Mon, 7 Aug 2006 16:11:15 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from localhost (localhost [127.0.0.1]) by pi.codefab.com (Postfix) with ESMTP id 0E4E15C8D; Mon, 7 Aug 2006 12:11:15 -0400 (EDT) X-Virus-Scanned: amavisd-new at codefab.com Received: from pi.codefab.com ([127.0.0.1]) by localhost (pi.codefab.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gMDiShUKvKj5; Mon, 7 Aug 2006 12:11:13 -0400 (EDT) Received: from [199.103.21.238] (pan.codefab.com [199.103.21.238]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by pi.codefab.com (Postfix) with ESMTP id DD2FA5C80; Mon, 7 Aug 2006 12:11:13 -0400 (EDT) In-Reply-To: <44D762AB.6010502@frii.com> References: <44D762AB.6010502@frii.com> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Charles Swiger Date: Mon, 7 Aug 2006 12:11:12 -0400 To: Steven H. Baeighkley X-Mailer: Apple Mail (2.752.2) Cc: freebsd-isp@freebsd.org Subject: Re: question about front page server extensions on freebsd X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Aug 2006 16:11:16 -0000 On Aug 7, 2006, at 11:56 AM, Steven H. Baeighkley wrote: > I have perused the mailing lists and some google searches but I > haven't > found an answer to this yet. It would seem that MS has pulled support > from frontpage server extensions for UNIX as of June 30, 2006. > > http://www.rtr.com/fpsupport/index.asp > > [ ... ] Are we dead in the water and stuck with our MS solution or > is there something else out there that is filling this need? I'm not sure-- I've been running web servers since 1993, and I have yet to use or need these FrontPage server extensions myself. Rumor has it that something called WebDAV, which comes bundled with newer versions of Apache, might be a suitable replacement. -- -Chuck From owner-freebsd-isp@FreeBSD.ORG Mon Aug 7 16:18:43 2006 Return-Path: X-Original-To: freebsd-isp@freebsd.org Delivered-To: freebsd-isp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3A88416A4DD for ; Mon, 7 Aug 2006 16:18:43 +0000 (UTC) (envelope-from jeff@norristechs.net) Received: from mail.norristechs.net (scooby.norristechs.net [71.36.89.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1B40943D5D for ; Mon, 7 Aug 2006 16:18:41 +0000 (GMT) (envelope-from jeff@norristechs.net) Received: from 63.71.72.19 with HTTP by webserver mail.norristechs.net ($virtual001) ; Mon, 7 Aug 2006 10:18:40 MDT Date: Mon, 7 Aug 2006 10:18:40 -0600 Message-Id: <200608071018.AA1114244@mail.norristechs.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii From: "Jeff Norris" X-Sender: To: Steven H. Baeighkley , Charles Swiger X-Mailer: Cc: freebsd-isp@freebsd.org Subject: Re: question about front page server extensions on freebsd X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: jeff@norristechs.net List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Aug 2006 16:18:43 -0000 If you really wanted to use FP2002 extentions. It's still available directly from Microsofts site. A quick google and I found it. http://www.microsoft.com/downloads/details.aspx?FamilyID=0c5eb0ad-e1ad-4100-9b76-8772a8220062&DisplayLang=en Be aware if you need support for frontpage exntions on UNIX (including LINUX). You can't use .htaccess for your own control, FP extentions uses .htaccess and will not work if you edit .htaccess or add directivies to it, as FP will replace the contents of that file. Convert to php , works a heck of alot better than FTP extentions. Cheers ~ Jeff. ---------- Original Message ---------------------------------- From: Charles Swiger Date: Mon, 7 Aug 2006 12:11:12 -0400 >On Aug 7, 2006, at 11:56 AM, Steven H. Baeighkley wrote: >> I have perused the mailing lists and some google searches but I >> haven't >> found an answer to this yet. It would seem that MS has pulled support >> from frontpage server extensions for UNIX as of June 30, 2006. >> >> http://www.rtr.com/fpsupport/index.asp >> >> [ ... ] Are we dead in the water and stuck with our MS solution or >> is there something else out there that is filling this need? > >I'm not sure-- I've been running web servers since 1993, and I have >yet to use or need these FrontPage server extensions myself. Rumor >has it that something called WebDAV, which comes bundled with newer >versions of Apache, might be a suitable replacement. > >-- >-Chuck > >_______________________________________________ >freebsd-isp@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-isp >To unsubscribe, send any mail to "freebsd-isp-unsubscribe@freebsd.org" > ________________________________________________________________ Sent via the WebMail system at mail.norristechs.net From owner-freebsd-isp@FreeBSD.ORG Thu Aug 10 13:24:34 2006 Return-Path: X-Original-To: freebsd-isp@freebsd.org Delivered-To: freebsd-isp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E1F8416A4DE for ; Thu, 10 Aug 2006 13:24:34 +0000 (UTC) (envelope-from mark@gaiahost.coop) Received: from biodiesel.gaiahost.coop (biodiesel.gaiahost.coop [64.95.78.120]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8E4EC43D49 for ; Thu, 10 Aug 2006 13:24:32 +0000 (GMT) (envelope-from mark@gaiahost.coop) Received: from gaiahost.coop (host-64-65-195-19.spr.choiceone.net [::ffff:64.65.195.19]) (AUTH: LOGIN mark@hubcapconsulting.com) by biodiesel.gaiahost.coop with esmtp; Thu, 10 Aug 2006 09:24:31 -0400 id 000A804B.44DB3390.000040DC Received: by gaiahost.coop (sSMTP sendmail emulation); Thu, 10 Aug 2006 09:24:36 -0400 Date: Thu, 10 Aug 2006 09:24:35 -0400 From: Mark Bucciarelli To: freebsd-isp@freebsd.org Message-ID: <20060810132435.GB2636@rabbit> Mail-Followup-To: freebsd-isp@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Subject: Ports/source dance X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Aug 2006 13:24:35 -0000 No port upgrade for rubygem-rail as of yet. No commits to CVS for the port either. :( The alert was posted only 16 hours ago, which isn't _that_ long. But rails is back at 1.1.2, which is already a version behind, so I expect I should upgrade rubygem-rails from source today. Should I create my own port (somehow, never done that) and install from that? Or is there an easier way? I guess the broader question is how to handle security upgrades when the port isn't ready. Thanks, m From owner-freebsd-isp@FreeBSD.ORG Thu Aug 10 20:38:52 2006 Return-Path: X-Original-To: freebsd-isp@freebsd.org Delivered-To: freebsd-isp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C8C1D16A4DD for ; Thu, 10 Aug 2006 20:38:52 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx23.fluidhosting.com [204.14.89.6]) by mx1.FreeBSD.org (Postfix) with SMTP id 4379E43D45 for ; Thu, 10 Aug 2006 20:38:51 +0000 (GMT) (envelope-from dougb@FreeBSD.org) Received: (qmail 24357 invoked by uid 399); 10 Aug 2006 20:38:49 -0000 Received: from localhost (HELO ?192.168.0.9?) (dougb@dougbarton.us@127.0.0.1) by localhost with SMTP; 10 Aug 2006 20:38:49 -0000 Message-ID: <44DB9955.10102@FreeBSD.org> Date: Thu, 10 Aug 2006 13:38:45 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 1.5.0.5 (Windows/20060719) MIME-Version: 1.0 To: freebsd-isp@freebsd.org References: <20060810132435.GB2636@rabbit> In-Reply-To: <20060810132435.GB2636@rabbit> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: Ports/source dance X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Aug 2006 20:38:52 -0000 Mark Bucciarelli wrote: > No port upgrade for rubygem-rail as of yet. No commits to CVS > for the port either. :( The alert was posted only 16 hours ago, > which isn't _that_ long. But rails is back at 1.1.2, which is > already a version behind, so I expect I should upgrade > rubygem-rails from source today. > > Should I create my own port (somehow, never done that) and > install from that? Or is there an easier way? > > I guess the broader question is how to handle security upgrades > when the port isn't ready. First off, you posted to the wrong list, you should have posted this to freebsd-ports@, ideally _after_ you contact the maintainer for the port (which can be found in the port's Makefile). To answer your question more usefully, the Porter's Handbook (on the FreeBSD web site) has a lot of good information about how to create and maintain ports. If you are lucky, the following will work for you for a quick and dirty update till the maintainer (or you) have a chance to do a more thorough job of it. If you're not lucky and need help, please follow up with the maintainer, and the freebsd-ports list if needed. cp -Rp /usr/ports//rubygem-rail ~/ cd ~/rubygem-rail vi Makefile Update version information to the desired version make makesum Use some out of band method to try and determine that the files you downloaded are the right ones make If that all works, then you can deinstall the old version and 'make install' the new one. Then of course it's up to you to conduct your typical quality assurance process to make sure that the new version works for you, etc. hth, Doug -- This .signature sanitized for your protection From owner-freebsd-isp@FreeBSD.ORG Thu Aug 10 20:49:42 2006 Return-Path: X-Original-To: freebsd-isp@freebsd.org Delivered-To: freebsd-isp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 040B616A4E2 for ; Thu, 10 Aug 2006 20:49:42 +0000 (UTC) (envelope-from mark@gaiahost.coop) Received: from biodiesel.gaiahost.coop (biodiesel.gaiahost.coop [64.95.78.120]) by mx1.FreeBSD.org (Postfix) with ESMTP id AA2E243D45 for ; Thu, 10 Aug 2006 20:49:41 +0000 (GMT) (envelope-from mark@gaiahost.coop) Received: from gaiahost.coop (host-64-65-195-19.spr.choiceone.net [::ffff:64.65.195.19]) (AUTH: LOGIN mark@hubcapconsulting.com) by biodiesel.gaiahost.coop with esmtp; Thu, 10 Aug 2006 16:49:39 -0400 id 000BC1DD.44DB9BE3.00005DF9 Received: by gaiahost.coop (sSMTP sendmail emulation); Thu, 10 Aug 2006 16:49:43 -0400 Date: Thu, 10 Aug 2006 16:49:43 -0400 From: Mark Bucciarelli To: freebsd-isp@freebsd.org Message-ID: <20060810204943.GG2164@rabbit> Mail-Followup-To: freebsd-isp@freebsd.org References: <20060810132435.GB2636@rabbit> <44DB9955.10102@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline In-Reply-To: <44DB9955.10102@FreeBSD.org> User-Agent: Mutt/1.4.2.1i Subject: Re: Ports/source dance X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Aug 2006 20:49:42 -0000 On Thu, Aug 10, 2006 at 01:38:45PM -0700, Doug Barton wrote: > Mark Bucciarelli wrote: > > > > I guess the broader question is how to handle security upgrades > > when the port isn't ready. > > First off, you posted to the wrong list, you should have posted this to > freebsd-ports@, ideally _after_ you contact the maintainer for the port > (which can be found in the port's Makefile). 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. > To answer your question more usefully, the Porter's Handbook > (on the FreeBSD web site) has a lot of good information about > how to create and maintain ports. If you are lucky, the > following will work for you for a quick and dirty update till > the maintainer (or you) have a chance to do a more thorough job > of it. If you're not lucky and need help, please follow up with > the maintainer, and the freebsd-ports list if needed. > > cp -Rp /usr/ports//rubygem-rail ~/ cd ~/rubygem-rail vi > Makefile Update version information to the desired version make > makesum Use some out of band method to try and determine that > the files you downloaded are the right ones make Heh. I looked at the patch for the upgrade from 1.0.0. to 1.1.2 and there were 14 seperate files changed across seven (IIRC) ports. I think I'll wait--turns out the versions I have running are not affected. Although if the maintainter doesn't get back to me in a week or so I may tackle it. Thanks, m From owner-freebsd-isp@FreeBSD.ORG Fri Aug 11 07:10:25 2006 Return-Path: X-Original-To: freebsd-isp@freebsd.org Delivered-To: freebsd-isp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B7BCA16A4E0 for ; Fri, 11 Aug 2006 07:10:25 +0000 (UTC) (envelope-from ady@fwd.ady.ro) Received: from nf-out-f131.google.com (nf-out-f131.google.com [64.233.182.131]) by mx1.FreeBSD.org (Postfix) with ESMTP id 67AEA43D49 for ; Fri, 11 Aug 2006 07:10:21 +0000 (GMT) (envelope-from ady@fwd.ady.ro) Received: by nf-out-f131.google.com with SMTP id x9so36387nfb for ; Fri, 11 Aug 2006 00:10:20 -0700 (PDT) Received: by 10.78.107.8 with SMTP id f8mr2046029huc; Fri, 11 Aug 2006 00:10:19 -0700 (PDT) Received: by 10.78.159.8 with HTTP; Fri, 11 Aug 2006 00:10:19 -0700 (PDT) Message-ID: <9e01a0da0608110010nb48e90fra21f149b836d32fa@mail.gmail.com> Date: Fri, 11 Aug 2006 10:10:19 +0300 From: "Adrian Penisoara" Sender: ady@fwd.ady.ro To: freebsd-isp@freebsd.org In-Reply-To: <20060810204943.GG2164@rabbit> MIME-Version: 1.0 References: <20060810132435.GB2636@rabbit> <44DB9955.10102@FreeBSD.org> <20060810204943.GG2164@rabbit> X-Google-Sender-Auth: 8f3946871f48b086 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-security@freebsd.org Subject: Re: Ports/source dance X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Aug 2006 07:10:25 -0000 Hi, On 8/10/06, Mark Bucciarelli 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 ? Regards, Adrian. Ady (@freebsd.ady.ro) From owner-freebsd-isp@FreeBSD.ORG Sat Aug 12 11:20:28 2006 Return-Path: X-Original-To: freebsd-isp@freebsd.org Delivered-To: freebsd-isp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C5D1016A4E0; Sat, 12 Aug 2006 11:20:28 +0000 (UTC) (envelope-from simon@zaphod.nitro.dk) Received: from mx.nitro.dk (zarniwoop.nitro.dk [83.92.207.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4FBC143D45; Sat, 12 Aug 2006 11:20:27 +0000 (GMT) (envelope-from simon@zaphod.nitro.dk) Received: from zaphod.nitro.dk (unknown [192.168.3.39]) by mx.nitro.dk (Postfix) with ESMTP id 1F5FE2DDCDC; Sat, 12 Aug 2006 11:20:26 +0000 (UTC) Received: by zaphod.nitro.dk (Postfix, from userid 3000) id 977811141D; Sat, 12 Aug 2006 13:20:25 +0200 (CEST) Date: Sat, 12 Aug 2006 13:20:25 +0200 From: "Simon L. Nielsen" To: Adrian Penisoara Message-ID: <20060812112024.GA1076@zaphod.nitro.dk> References: <20060810132435.GB2636@rabbit> <44DB9955.10102@FreeBSD.org> <20060810204943.GG2164@rabbit> <9e01a0da0608110010nb48e90fra21f149b836d32fa@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9e01a0da0608110010nb48e90fra21f149b836d32fa@mail.gmail.com> User-Agent: Mutt/1.5.11 Cc: freebsd-isp@freebsd.org, freebsd-security@freebsd.org Subject: Re: Ports security [was: Ports/source dance] X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Aug 2006 11:20:28 -0000 On 2006.08.11 10:10:19 +0300, Adrian Penisoara wrote: > On 8/10/06, Mark Bucciarelli 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