[9744] in bugtraq
Re: Frontpage extensions under Apache 1.3.4
daemon@ATHENA.MIT.EDU (pedward@WEBCOM.COM)
Tue Feb 23 11:32:48 1999
Date: Mon, 22 Feb 1999 09:17:01 -0800
Reply-To: pedward@WEBCOM.COM
From: pedward@WEBCOM.COM
X-To: sitz@onastick.net
To: BUGTRAQ@NETSPACE.ORG
In-Reply-To: <Pine.LNX.4.05.9902041857530.19214-100000@stanis.onastick.net>
from "Sitzkrieg Redundus" at Feb 19, 99 06:31:23 pm
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. /\
