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 () perryat_private Networks and Administration Think Blue. /\
This archive was generated by hypermail 2b30 : Fri Apr 13 2001 - 14:37:04 PDT