Release notes for Symantec Protection Engine for Network Attached Storage 7.0

Article:TECH196149  |  Created: 2012-09-05  |  Updated: 2012-09-09  |  Article URL http://www.symantec.com/docs/TECH196149
Article Type
Technical Solution


Issue



This document contains the release notes for Symantec Protection Engine for Network  Attached Storage 7.0


Solution



Problem Description: Symantec Scan Engine SNMP trap feature is not working as expected.
Resolution: Fixed.

Problem Description: Please change min. required JRE from "6.0" to "6.0 update XX or later", as it's for JRE 5.0
Resolution: Fixed.

Problem Description: Documentation needs update on how to configure the SPE to pick up defs from internal LU websites and distribution points using UNC path.
Resolution: Fixed.

Problem Description: symcscan.mib file has a typo at line 878
Resolution: Fixed.

Problem Description: Graceful shutdown always fails after 5.2.10
Resolution: Fixed.

Problem Description: Support is requesting that the category3.xml "FilerPerformanceThreshold" parameter be moved to category2.
Resolution: Fixed.

Problem Description: "systemAuthenticationError" is mis-spelled in trap 52 in symcscan.mib file
Resolution: Fixed.

Problem Description: Support is requesting that the category3.xml "FileSizeScanThreshold" parameter be moved to category2.
Resolution: Fixed.

Problem Description: Client IP address field and before field are missing sometimes in a log file. Is it intended behavior?
Resolution: Fixed.

Problem Description: Files above FileSizeScanThreshold are being copied locally forcing an abort timeout on the Filer
Resolution: Fixed.

Problem Description: Queries: Cannot detect the EICAR sometimes
Resolution: Fixed.

Problem Description: The "log bind address" field does not apply to SNMP traps.
Resolution: Fixed.

Problem Description: The extra OPTIONS request is getting executed every time while scanning a file with SSE.
Resolution: Fixed.

Problem Description: Memory leak in ssecls
Resolution: Fixed.

Problem Description: "ScanClientStreamStart API has a memory leak"
Resolution: Fixed.

Problem Description: The Command Line Scanner will report infected file deleted, even when it fails to delete the infected file.
Resolution: Fixed.

Problem Description: "ScanClientStreamStart API has a memory leak" - Need to correct sample example.cpp that goes with SSE Package.
Resolution: Fixed.

Problem Description: Java CLS produces an error when scanning large files (~1GB) and Scan Engine is installed on RHEL 5.6.
Resolution: Fixed.

Problem Description: Java API is modifing the filepath to scan if the path has a path structure different than that of the local OS.
Resolution: Fixed.

Problem Description: SSE CSDK command line scanner for Linux causes "double free or corruption (!prev)" error" if -log option is used during scan
Resolution: Fixed.

Problem Description: Network Security Analyzer reports that SSE uses weak SSL Ciphers.
Resolution: Fixed.

Problem Description: SSE login screen is not centered in browser window
Resolution: Fixed.

Problem Description: Update the default "Access Denied Message" text for URL filtering.
Resolution: Fixed.

Problem Description: Update output for URL Filtering ${REASON.EN_US} variable.
Resolution: Fixed.

Problem Description: Need to correct sample example.cpp code provided in 'Symantec™ Scan Engine Software Developer's Guide' document for C API
Resolution: Fixed.

Problem Description: In the ScanClientStreamStart (Page87:Table4-16),the description of return code 7 is insufficient.
Resolution: Fixed.





Article URL http://www.symantec.com/docs/TECH196149


Terms of use for this information are found in Legal Notices