
Understanding Flash Communication Server Security 51
• Application.xml
The
<JSEngine>:<RuntimeSize> tag lets you limit the amount of memory that can be used
by the server-side ActionScript on the virtual host. This can help prevent attacks using very
large numbers of scripts. The default is 1024K.
The
<StreamManager>:<StorageDir> and <SharedObjManager>:<StorageDir> tags let
you specify the locations for storing streams and shared objects. This allows you to store them
in locations outside your web publishing directory and outside your flashcom application
directory if you wish.
The
<Bandwidth> tags groups let you specify the maximum amount of data that an
application can send and receive.
For more detailed information about the server’s XML tags, see Chapter 3, “Configuring Flash
Communication Server,” on page 25.
Place source and data files carefully. To prevent hackers from gaining access to the source files of
your applications, avoid placing sensitive files in your web server’s publishing directory. If you
have a web server, the Administration Console (admin.swf) and sample applications are installed
by default in your web server’s publishing directory. During deployment, do not locate Flash
Communication Server application source or data files (FLA, FLV, ASC) or the flashcom
application directory in the web publishing directory; keep only your applications’ SWF and
HTML files in the publishing directory.
Protect configuration files. In addition to its communication streams, the server’s configuration
files should be protected. To ensure that the server’s XML files and directory structure cannot be
accessed by unauthorized users, place the server computer in a physically secure location and
password-protect the operating system so that only the appropriate server administrators have
access.
About authentication and authorization
To authenticate (validate) administrators, Flash Communication Server employs several layers of
host-based user security. (Host-based security refers to security measures that are implemented in
the server software itself.) When a user tries to connect to the Administration Console with an
administrator user name and password, the server uses the layers of settings in its XML
configuration files to determine whether the connection should be allowed. Only administrators
who have been explicitly defined can connect to the server to use the Administration Console.
The server authenticates administrators by evaluating the contents of the XML tags in the
following order:
1 Server.xml file: <Allow>, <Deny>, and <User> tags. These tags indicate whether a user is
allowed to connect to the Administration Console from the current IP address. Administrators
can connect only from IP addresses you have specified with these tags.
2 Adaptor.xml file: <Allow> and <Deny> tags. These tags indicate whether a user is allowed to
connect to the specified adaptor from their current IP address.
3 Vhost.xml file: <Allow> and <Deny> tags. These tags indicate whether a user is allowed to
connect to the specified virtual host from the current IP address.
The server authenticates administrators by comparing their user names and passwords to those
defined in the Server.xml file. When you choose these names and passwords, make sure they are
not simple ones that can be easily guessed.
Commentaires sur ces manuels