From owner-freebsd-ports@FreeBSD.ORG Fri Apr 22 18:46:02 2005 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CC82B16A4CE for ; Fri, 22 Apr 2005 18:46:02 +0000 (GMT) Received: from outbound0.sv.meer.net (outbound0.sv.meer.net [205.217.152.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7547F43D53 for ; Fri, 22 Apr 2005 18:46:02 +0000 (GMT) (envelope-from jrhett@mail.meer.net) Received: from mail.meer.net (mail.meer.net [209.157.152.14]) j3MIfYrd083150; Fri, 22 Apr 2005 11:46:00 -0700 (PDT) (envelope-from jrhett@mail.meer.net) Received: from mail.meer.net (localhost [127.0.0.1]) by mail.meer.net (8.12.10/8.12.10/meer) with ESMTP id j3MIcJuR059621; Fri, 22 Apr 2005 11:38:29 -0700 (PDT) (envelope-from jrhett@mail.meer.net) Received: (from jrhett@localhost) by mail.meer.net (8.12.1/8.12.10) id j3MIcHvI059612; Fri, 22 Apr 2005 11:38:17 -0700 (PDT) (envelope-from jrhett) Date: Fri, 22 Apr 2005 11:38:17 -0700 From: Joe Rhett To: Scot Hetzel Message-ID: <20050422183816.GB45992@meer.net> References: <892CC2C451D0414B90159D10B5BDAA65AB2234@EXCHANGE.astate.edu> <20050207202417.GB37923@meer.net> <20050208004233.GA84236@xor.obsecurity.org> <790a9fff050208142045266974@mail.gmail.com> <20050224203342.GH49530@meer.net> <790a9fff05022414531dd27600@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <790a9fff05022414531dd27600@mail.gmail.com> User-Agent: Mutt/1.4i Organization: Meer.net LLC cc: ports@freebsd.org cc: Todd Reed Subject: Re: FreeBSD Port: frontpage-5.0.2.2623_1 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Apr 2005 18:46:03 -0000 Sorry for the very late reply, been busy... On Thu, Feb 24, 2005 at 04:53:09PM -0600, Scot Hetzel wrote: > On Thu, 24 Feb 2005 12:33:43 -0800, Joe Rhett wrote: > > Why rename the port? You've fixed the main frontpage port to use the > > rtr-supplied binaries. Why is mod_frontpage being renamed instead of > > reused? > > > The www/mod_frontpage port wasn't renamed, as it still exists. This > port uses sources from "Improved mod_frontpage" which was an attempt > to replace having to use a patched Apache server (i.e. the old > www/apache-fp port). > > With the recent versions of the RTR FrontPage Extensions, no patching > the Apache server was required to use their mod_frontpage module. > > Because the new "RTR mod_frontpage" version (www/mod_frontpage*-rtr) > is not compatible with the old "Improved mod_frontpage" version > (www/mod_frontpage). Um, works fine for me after using the patches I submitted! And it has significant security improvements over your version here. > I did add some features from the Improved mod_frontpage: > - Allow/Disallow Client to publish with FrontPage Extensions > - Allow/Disallow Administration of web site with FrontPage Extensions > > But I used 2 options (FrontPage [on,off] / FrontPageAdmin [on,off]) > instead of 4 options (FrontPageEnable,FrontPageDisable / > FrontPageAdminEnable,FrontPageAdminDisable). > > The RTR mod_frontpage module doesn't disable the FrontPage Extensions > (unless the port is compiled with WITH_DISABLED). The Improved > mod_frontpage defaults to disabling the FrontPage Extensions, until > FrontPageEnable and/or FrontPageAdminEnable are added to the > httpd.conf file. > > www/mod_frontpage*-rtr can be made compatible with Improved > mod_frontpage when WITH_MODFP_COMPAT and WITH_DISABLED are used to > build the port. So clarify for me again why this is better? It seems that adding the submitted patches (4 months old now?) to the improved mod_frontpage would be better than trying to back-hack these things into the rtr version of the module. Improved mod_frontpage has other significant significant security enhancements as well. -- Joe Rhett senior geek meer.net