Bugtraq mailing list archives
Re: Frontpage extensions under Apache 1.3.4
From: pedward () WEBCOM COM (pedward () WEBCOM COM)
Date: Mon, 22 Feb 1999 09:17:01 -0800
This is a problem that I encountered as well. The solution to this was to create a whole new tree of config files which the http server did not actually use. The advantage was that the http server can do things better without all the cruft Frontpage adds, and Frontpage was happy because it could modify the config files, and they didn't bother the webserver. So, just create a dummy tree of config files with the information Frontpage wants, and make it run against that. I believe that the /usr/local/frontpage/<domain>:<port> file contained the path to the config files. I just made a custom script for installing Frontpage, which created the dummy files. YASFPSI (Yet Another Stupid FrontPage Security Issue). --Perry
Great. Except that when creating a root web, fp_install.sh calls fpsrvadm.exe, which moves the file specified by the "ResourceConfig" directive "file.bak" and installs its own. Thus, on systems running the Noah Robin
-- Perry Harrington Director of System Architecture zelur xuniL () perry () webcom com Networks and Administration Think Blue. /\
Current thread:
- Frontpage extensions under Apache 1.3.4 Sitzkrieg Redundus (Feb 19)
- Re: Frontpage extensions under Apache 1.3.4 Alan Brown (Feb 21)
- Re: Frontpage extensions under Apache 1.3.4 Frank Miller (Feb 22)
- Re: Frontpage extensions under Apache 1.3.4 greg (Feb 22)
- Re: Frontpage extensions under Apache 1.3.4 pedward () WEBCOM COM (Feb 22)
- <Possible follow-ups>
- Re: Frontpage extensions under Apache 1.3.4 Paul Schandel (Feb 22)
- Re: Frontpage extensions under Apache 1.3.4 Alexander Sanda (Feb 22)
- Re: Frontpage extensions under Apache 1.3.4 Frank Miller (Feb 23)
- Re: Frontpage extensions under Apache 1.3.4 Alan Brown (Feb 21)