==========================================================================
 Post-Release Fix for
 F-Secure Anti-Virus for Internet Gateways

 Copyright (c) 1993-2004 F-Secure Corporation. 
 All Rights Reserved.
==========================================================================

SUMMARY

This post-release fix is for the following products/versions:
 o F-Secure Internet Gatekeeper 6.40
 o F-Secure Internet Gatekeeper 6.41

If you use earlier versions of the above mentioned products, please 
download and install the latest version.

This post-release fix includes the following fixes:
 o CTS#35587 The product may malfunction under high load
 o CTS#35589 Each RTRC item has an unused FMutex
 o CTS#35665 Rotatelogs.exe is not shut down if httpscan.exe terminates unexpectedly
 o CTS#35721 Unhandled Exception in fs_filter if URI is empty and no '/' at the end
 o CTS#35997 Problems listening to internet radio stations
 o CTS#36079 Multiple "temporary file can't be created..." errors in LogFile.log  
 o CTS#36108 SCIPMaxInmemSize is treated in bytes
 o CTS#36131 Hostname in list of trusted hosts causes exception in FSFILTER

Recommendation: It is recommended to apply this hotfix.

TECHNICAL DETAILS

SCR#35587 description:

Under high loading the product seemingly stops accepting new connections and
has to be manually restarted to get it back into operation. Although in some
situations the problem can be worked out by changing Windows TCP/IP registry
options and some product settings, the product reportedly still malfunctions
after running under high loading for a while. This fix improves the error and
exception handling logic and makes the product more reliable.

SCR#35589 description:

It was found that the product used system resources inefficiently. For each 
item in the Recent Transaction Results Cache (RTRC), it allocated a mutex
object which was not actually used. The problem is fixed in this post-release
fix.

SCR#35665 description:

If the child httpscan.exe process terminates unexpectedly, there are two 
instances of rotatelogs.exe process left running in the system. Although
abandoned rotatelogs.exe processes do not pose a severe problem, they waste
system resources and may be a reason of resource exhaustion under some
circumstances. 

SCR#35721 description:

It was found that the product could terminate unexpectedly due to an 
unhandled exception when processing an empty URI or URI path without the 
slash ("/") at the end. The problem is fixed in this post-release fix.

SCR#35997 description:

This problem is partially caused by the problem found in SCR#35721. It was
also found that the product did not properly handle RSTP (Real Time Streaming 
Protocol). Because of this, end-users could not listen to Internet radio stations 
with RealPlayer or other radio/media player software when configured to use 
FS Internet Gatekeeper as a HTTP proxy. When this hotfix is applied, it should
be possible to listen to Internet radio stations through FS Internet Gatekeeper
without glitches.

SCR#36079 description:

Logfile.log contained quite many errors like "A temporary file cannot be 
created due to error: The given path misformatted or contained invalid 
characters". It was found that under certain conditions the product could
attempt to create temporary files with invalid filenames. Because of the
error, a request under processing was blocked. The logic of generating names 
for temporary files has been improved in this hotfix.

SCR#36108 description:

It was found that the product treated the Max Size of Data Processed In-Memory
setting (the SCIPMaxInmemSize directive in httpd.conf) in bytes instead of 
kilobytes. Because of that, the performance of the product could be worse than
anticipated. After applying this hotfix, the setting should be treated in
kilobytes as expected.

SCR#36131 description:

When a host is specified as FQDN (Fully Qualifed Domain Name) in the Trusted 
Hosts table, the product fails to process a request from that host and 
unhandled exception is reported to the error.log. The problem is fixed in 
this hotfix.

OTHER INFORMATION

This post-release fix includes the following files:

File Name            File Version      MD5 Checksum
-----------------------------------------------------------------------
fsavigwd.exe         6.40.91           e1f09cf0662891ec3315563e7e98007a
httpscan.exe         6.40.91           599790752ccc371410f8cfb4741182f2
libapr.dll           0.0.0.0           345c22ecd78f372436a27d5572f9b5ce
libaprutil.dll       0.0.0.0           58f90669643735542292e94c5d0a6f47
libhttpd.dll         6.40.91           7a0b7cf813204e4b9011bac5526b1b98
rotatelogs.exe       6.40.91           d5c2ae10a95a193de421d0276b649c98
mod_fs_filter.so     6.40.91           e1092547e5a46e32a24b2a0db133562b
mod_proxy.so         0.0.0.0           ac4795366f2d4fcda55ec96d1508d86d
mod_proxy_connect.so 0.0.0.0           c0f592d99156b74d7ed057657c5249d9
mod_proxy_ftp.so     0.0.0.0           09e59a04b4994a97ba4173e7f2fccfe7
mod_proxy_http.so    0.0.0.0           df4d344fef6b64f6080967bca60170ee

NOTE: Fixes for a particular component are cumulative and contain all 
of the previous fixes for that component. 

For additional information, please visit F-Secure Support Center at:
http://support.f-secure.com/

HOW TO APPLY THE POSTFIX LOCALLY

o Unpack all files from the package into a temporary folder on the
  local machine.

o Open this folder in Windows Explorer and then double-click 
  "fsavigw640-01.fsfix".

-- end of file --