MACROMEDIA FLASH MEDIA SERVER 2-MANAGING FLASH MEDIA..., Manual

Page: 217 / 238

Managing server security 217
The
MaxAppInstances
tag nested in the
ResourceLimits container
lets you limit the
number of application instances that can exist simultaneously on the virtual host. This can
help prevent denial-of-service attacks. The default is -1, which allows unlimited
application instances.
The
MaxStreams
tag nested in the
ResourceLimits container
lets you specify the
maximum number of streams that can exist simultaneously on the virtual host. This can
help prevent denial-of-service attacks. The default is -1, which allows unlimited streams.
The
MaxSharedObjects
tag nested in the
ResourceLimits container
lets you specify
the maximum number of shared objects that can exist simultaneously on the virtual host.
This can help prevent denial-of-service attacks. The default is -1, which allows unlimited
shared objects.
■
Application.xml file
The
RuntimeSize
tag nested within the
JSEngine
container 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
and
SharedObjManager
tags nested in the
StreamManager
container let you specify the locations for storing streams and shared objects. You can store
them in locations outside the applications directory in the Macromedia Flash Media
Server directory, if you wish.
The
Bandwidth
tags groups let you specify the maximum amount of data that an
application can send and receive.
For detailed information about the server’s configuration files, see Chapter 3, “Configuration
Files.”
Place source and data files carefully
To prevent hackers from gaining access to the source
files of your applications, do not place sensitive files in your web server’s publishing directory.
If you have a web server, the management console (fmsconsole.swf ) is installed by default in
your web server’s publishing directory. During deployment, do not place Flash Media Server
application source or data files (FLA, FLV, ASC) or the applications directory (installed by
default in the Flash Media Server directory) in the web publishing directory; keep only your
SWF and HTML files in the publishing directory.
Protect configuration files In addition to its media streams, the server’s configuration files
should be protected. To ensure that the server’s configuration 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.