Sun Microsystems Netscape Enterprise Server, Руководство администратора

Страница: 481 / 532

Appendix D, Server Extensions for Microsoft FrontPage 481
Overview
administrator enforce different end-user, author, and administrator permissions
on each FrontPage web, since FrontPage uses the server’s built-insecurity
mechanism to control access.
Domain Names And Frontpage Webs
FrontPage webs can be implemented on a Enterprise Server and accessed by
web browsers in the following ways:
• As private domain names, such as
www.mycompany.com
. These are
usually implemented as virtual servers on the same physical server machine
using multi-hosting. Private domain name customers each get their own
root web and have the option of creating sub-webs.
• As a common or shared domain but with private virtual servers, as in
www.mycompany.myprovider.com
, where
myprovider.com
is a
shared domain and
www.mycompany
is a private virtual server. Private
virtual server customers on a shared domain each get their own root web
and have the option of creating sub-webs.
• As a URL on an Internet service provider’s server machine, as in
www.myprovider.com/mycompany
. URL customers get a single sub-
web.
Security Issues
FrontPage implements web security on your web server by changing the
access-control lists (ACLs) for all files and directories in each FrontPage web.
Installing FrontPage always modifies the ACLs of the Server Extensions stub
executables contained in the
/_vti_bin
directory in each web. A new
installation of FrontPage will additionally modify the ACLs of the web content
files, but an upgrade of an existing installation of the Server Extensions will not
modify the content file ACLs and consequently will leave the security settings at
a less secure level than the default FrontPage settings. You can upgrade the
ACLs of your web content by using the Check and Fix option of the FrontPage
Server Administrator utility.