Symptoms:
This page contains the release notes for Symantec Scan Engine 5.0.1 - 5.1.9 in-line release build. This document is written so that the most recent product builds are added to the beginning of the document.

Solution:
Symantec Scan Engine 5.1.9

Symptom: Symantec Scan Engine 5.1 does not initialize the bzip2 engine.
Solution: Fixed.

Symptom: Outbreak Event occurs only twice in Symantec Scan Engine 5.1.8.
Solution: Fixed.

Symptom: Symantec Scan Engine consumes all CPU resource while scanning.
Solution: Fixed.

Symantec Scan Engine 5.1.8

Symptom: File triggers false positive, when scanned by Scan Engine 5.1.
Solution: Fixed.

Symptom: SSE install script does not detect the presence of non-global zones on Solaris 10.
Solution: New build supports both global and non-global zone installation.

Symptom: If ‘Outbreak’ option is enabled on ‘Same Virus Infections’, SSE crashes as soon as an Outbreak is triggered.
Solution: Fixed.

Symptom: SSE cannot show log entries if a file name or URL contains the symbol '|'.
Solution: Fixed. URL encoding format is applied to encode '|' symbol.

Symptom: RFC issue with Scan Engine’s ICAP response.
Solution: Fixed RFC compliance issue.

Symptom: Scanfile Failure error.
Solution: Fixed.

Symptom: SSE fails to upgrade from SSE5.1.7 to SSE 5.1.8.35 with existing settings.
Solution: Fixed.

Symantec Scan Engine 5.1.7

Symptom: Scan Engine decomposer reports .CAT file as a malformed MIME container.
Solution: Updated CSAPI.

Symptom: Eicar.com is not detected in .ZOO and .HYP files.
Solution: At present, ZOO and HYP archive types are not supported. The README file is updated accordingly.

Symptom: CPU usage spikes for a long time when scanning a specific email file.
Solution: Updated CSAPI.

Symptom: SSE installation on Red Hat Linux Advanced Server 2.1 fails.
Solution: Red Hat Linux AS 2.1 is not supported by Symantec Scan Engine version 5.1.6 onwards. The README file is updated accordingly.

Symantec Scan Engine 5.1.6
 
Symptom: When using Scan Engine in RPC mode, it is not logging one of the errors sent to the Filer.
Solution: As a workaround, set the "FilerPerformanceThreshold" (cat-3) parameter to an appropriate value.
 
Symptom: Scan Engine does not log Filer retry errors.
Solution:  After the maximum number of reconnect attempts, Scan Engine will now log the message: "Symantec Scan Engine has exceeded the maximum number of attempts and hence disconnected from the RPC client."
 
Symptom: Scan Engine does not support non-ASCII characters in file extensions.
Solution: Scan Engine will now log the filenames it receives from the RPC client correctly.
 
Symptom: Problems upgrading from Scan Engine 4.3 to 5.1 when Scan Policy is set to "SCANDELETE."
Solution: The upgrade script was modified to correct this problem.
 
Symptom: ScanFileSave feature does not work when multiple parameter are configured
Solution: Removed initial verification of "ScanFileSaveSettings" (cat-3) parameter, as it is already present in ScanFileSave feature implementation.
 
Symptom: Command line scanner does not return the Threat Category ID for NonViral Threat.
Solution: Added Category ID detection for viral threats to Command line scanner.
 
Symptom: Command line scanner displays a segmentation fault when "recurse" switch is used to scan nested directory.
Solution: Fixed
 
Symptom: After performing a preservation install from 4.3 to 5.1, the AdminPort setting is not preserved.
Solution: Fixed
 
Enhancement: Integrated CSAPI 8.1.0.3.

Enhancement:  Added GCC 3.4.6 compiler support for ScanEngineAPI on Red Hat Enterprise Linux 3 and 4.
 
Symantec Scan Engine 5.1.5
 
Enhancement: Red Hat Enterprise Linux 4.0 is now a supported Operating System.

Symantec Scan Engine 5.1.4

Symptom: RSA Crypto Libraries have vulnerabilities prior to Crypto-C version 6.3.1 and Cert-C version 2.8.
Solution: Upgraded RSA libary to version 6.3.1 which includes new CSAPI integration.

Symptom: Newly integrated CSAPI version doe snot support arc and ln type archive files.
Solution: The configuration.xml in the section: "/configuration/resources/DecEngine/@value" cannot contain the types: "arc" or "ln".

Symptom: Filer outage caused by particular doc file which causes all scanning threads to be busy in scan engine.
Solution: File scanning halted when it meets or exceeds set maximum extract time for container file.

Symptom: SDK does not compile on Solaris 10.
Solution: Support added for Solaris 10 with gcc-3.4.6.

Symptom: On Windows platform cannot create log files at a shared drive.
Solution: Changed Readme.txt file section on User Interface / Logging to describe steps on how to use shared drive.

Symptom: ICAP response for non viral threat detection does not include category name.
Solution: Modified code to send category name in ICAP response based on value of configuration item. This value found in configuration.xml file in the @value section.

Symptom: Readme.txt contains no recommended value for RAM value of In-memory file system.
Solution: Added new section: "Maximum RAM used In-memory file system" configuration parameter to Readme.txt.

Symptom: No information found in Readme.txt on behavior of Scan Engine when maximum limit of reconnect attempts to RPC client reached.
Solution: Added new section: "working with RPC protocol" to errata section of Readme.txt file.

Symantec Scan Engine 5.1.3

Symptom: During installation on a Windows computer, if the user specifies the log directory, and that directory exists, the installation routine still attempts to create the directory which results in an error.
Solution: Added validation for directory creation to avoid attempting to create existing directories.

Symptom: Users cannot access the Scan Engine Interface because the Symantec Code Signing certificate is expired.
Solution: Jars are re-signed upto Sep 2009 with valid certificate.

Symantec Scan Engine 5.1.2

Symptom: Scan Engine Interface is inaccessible because Symantec Code Signing certificate is expired.
Solution: Jar code was re-signed with valid certificate.

Symptom: Space characters in the Korean date format caused validation errors.
Solution: Updated the product to consider space characters as part of date validation in Korean locale.

Symptom: Multiple email addresses are separated by semicolon in To: field of SMTP Alert messages. This practice is not compliant with RFC 822.
Solution: Updated the product to separate multiple email addresses in the To: field with commas instead of semicolons.

Enhancement: Added an optional X-URL-Blocked-Domain to the ICAP response for URL filtering request. This field contains a domain name and is only sent when a URL is blocked at the domain level.

Enhancement: Added field to user interface to configure primary and secondary SNMP ports. If no custom SNMP port is used, the Symantec Scan Engine uses the default SNMP port.

Enhancement: Added support for administrator console access with Mozilla Firefox on all platforms on which Symantec Scan Engine runs.

Enhancement: Added Microsoft Operations Manager (MOM) management pack to support the alerts and events from Symantec Scan Engine 5.1. MOM has a Knowledge Base tab for each alert.Administrators. You can click this tab to learn about recommended actions for a particular event or alert.

Symantec Scan Engine 5.1.1

Symptom: Readme does not state the user interface (UI) can only be accessed through an HTTPS connection.
Solution: Readme file updated.

Symptom: Update Readme with additional notes not added in the 5.1.0 readme.
Solution: Readme file updated with additional notes.

Symptom: CD version of Readme file references invalid versions of Java for Scan Engine operation.
Solution: CD Readme file updated. References to invalid versions of Java removed.

Enhancement: Customer request the generation of a log message when Scan Engine loses connection with the RPC filter.
Solution: New log message added and generates when a disconnect occurs. Message sent to SMTP, local, and NT Event logs.

Symantec Scan Engine 5.0.2

Symptom: Some files were incorrectly being identified as viral by the Bloodhound engine.
Solution: Modified internal detection engine to handle the files correctly.

Symantec Scan Engine 5.0.1

Symptom: Symantec Scan Engine does not support Red Hat Enterprise 2.1.
Solution: Updated product to support Red Hat Enterprise 2.1.

Document ID: 2005111415303154
Last Modified: 10/02/2008
Date Created: 11/14/2005
Operating System(s): Red Hat Linux 9.0, Red Hat Enterprise Linux 2.1, Red Hat Enterprise Linux 3.0, Red Hat Linux Advanced Server 2.1, SuSE Linux Enterprise Server 8.0, Solaris 9
Product(s): Symantec Scan Engine 5.0 - UNIX, Symantec Scan Engine 5.0 - Windows, Symantec Scan Engine 5.1
Release(s): SSE 5.0, SSE 5.0 [All Releases], SSE 5.0.1, SSE 5.1