SPE For NAS Release Notes
SPE For NAS Release Notes
Symantec, the Symantec Logo, the Checkmark Logo and are trademarks or registered trademarks of
Symantec Corporation or its affiliates in the U.S. and other countries. Other names may be trademarks
of their respective owners.
The product described in this document is distributed under licenses restricting its use, copying, distribution,
and decompilation/reverse engineering. No part of this document may be reproduced in any form by any
means without prior written authorization of Symantec Corporation and its licensors, if any.
THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS,
REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE
DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY
INVALID. SYMANTEC CORPORATION SHALL NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL
DAMAGES IN CONNECTION WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS
DOCUMENTATION. THE INFORMATION CONTAINED IN THIS DOCUMENTATION IS SUBJECT TO
CHANGE WITHOUT NOTICE.
Symantec Corporation
350 Ellis Street
Mountain View, CA 94043
https://www.symantec.com
Symantec Support
All support services will be delivered in accordance with your support agreement and the
then-current Enterprise Technical Support policy.
■ System requirements
■ Known issues
version 1.0 of ICAP, as presented in RFC3507 (April 2003). Symantec also has developed
connector code for some third party applications to seamlessly integrate with Symantec
Protection Engine.
The Symantec Protection Engine Software Developers Guide provides information about how
to create customized integrations with ICAP.
Feature Description
Support for non-archive files Symantec Protection Engine 8.1 supports the scanning of the
larger than 2 GB non-archive files that are larger than 2 GB. The support is limited to
2 GB in previous releases.
Latest Symantec technologies Symantec Protection Engine 8.1 is integrated with latest internal
Symantec scanning technologies.
Enhanced LiveUpdate Internal critical fixes are now delivered through LiveUpdate.
Improved in-memory file system Symantec Protection Engine uses the system memory to stream and
scan the files. Now, the memory size is no more limited to 4 GB.
8.0.x Symantec Protection Engine 8.1 supports an upgrade from version 8.0.x.
You can choose to upgrade the product and preserve your existing settings or
perform a clean upgrade. If you choose to do a clean upgrade, the installer
removes the previous version, and then installs the newer version as a full
installation, without preserving any previous settings.
Release Notes 6
Migrating to version 8.1
7.9.x Symantec Protection Engine 8.1 supports an upgrade from version 7.9.x.
You can choose to upgrade the product and preserve your existing settings or
perform a clean upgrade. If you choose to do a clean upgrade, the installer
removes the previous version, and then installs the newer version as a full
installation, without preserving any previous settings.
7.8.x Symantec Protection Engine 8.1 supports an upgrade from version 7.8.x.
You can choose to upgrade the product and preserve your existing settings or
perform a clean upgrade. If you choose to do a clean upgrade, the installer
removes the previous version, and then installs the newer version as a full
installation, without preserving any previous settings.
7.5.x Symantec Protection Engine does not support direct upgrades from
version 7.5.x. You must migrate to 8.0 first, then upgrade to 8.1.
LD_LIBRARY_PATH="<Base_Location>
/SPE_Tools/Migration_Utility/RedHat/"
7.0.x Symantec Protection Engine does not support direct upgrades from
version 7.0.x. You must first upgrade to version 7.5.x, then migrate
to 8.0.
You must stop the Symantec Protection Engine service before you upgrade the software.
Release Notes 7
System requirements
System requirements
Before you install Symantec Protection Engine, verify that your server meets the minimum
system requirements.
■ System requirements to install Symantec Protection Engine on Linux
For Symantec Protection Engine platform support matrix, see the following pages:
■ Symantec Protection Engine for Cloud Services
https://support.symantec.com/en_US/article.DOC11401.html
■ Symantec Protection Engine for Network Attached Storage
https://support.symantec.com/en_US/article.DOC11402.html
Ensure that your operating system has the latest service patches available.
Processor Intel or AMD Server Grade Single Processor Quad Core systems or higher
Hardware ■ Network interface card (NIC) running TCP/IP with a static IP address
■ Internet connection to update definitions
■ 100 Mbps Ethernet link (1 Gbps recommended)
Release Notes 8
System requirements
Note: If any of the above package binary is already present on the computer and if the
installer is still unable to find it, you can add the path to the binary in
LD_LIBRARY_PATH environment variable.
Release Notes 9
Known issues
The following Linux guest operating systems have been certified on Hyper-V:
Known issues
■ XMLModifier does not show error for inactive XPath if you use incomplete XPath by skipping
a child node with two slashes (//).
Some configurations of previous release are no more valid in Symantec Protection Engine
8.1. However, XML files still contain those configurations. You cannot configure these
values using XMLModifier tool. If you run the XMLModifier command with such inactive
XPath, you get the following error:
XPath is not active in Symantec Protection Engine 8.1 and later versions.
Symantec Protection Engine does not support inactive XPaths.
Ensure that you always use the complete XPath in the command. If you use incomplete
XPath by skipping a child node with two slashes (//), XMLModifier does not show error
even if XPath is inactive.
■ Symantec Protection Engine does not support the scanning of the following container files:
LZH, LHA, AMG, TNEF.
■ For top-level encrypted zip file, Symantec Protection Engine does not attach a text
notification file to the email. Instead, email has a zip file as an attachment, which contains
a text notification file in place of encrypted file.
■ If Symantec Protection Engine detects infected files within multiple levels of archive files,
it reports only the file name and not the relative path of the file.
■ Scan time out in Symantec Protection Engine is a coarse-grained timeout. It tries to timeout
at the nearest possible opportunity and may not be precise.
■ MaxContainerExtractSize configuration does not work for .TAR and .7Z files.
■ MaxExtractFileCount configuration does not work for .TBZ and .TGZ files.
■ ICAP response for the encrypted container violation does not contain the file name for
which the violation has happened.
■ Symantec Protection Engine sometimes does not respond while scanning an archive file
on CentOS and RHEL 6.8 platforms.
Release Notes 10
Where to get more information
The old version of CentOS/RHEL component GNU C Library (glibc) causes this issue.
Update this component to the latest version to resolve this issue. In CentOS 7.4, update
the component to version 2.17.260.
■ Microsoft Office application report shows that recovery error message after malware is
replaced.
Microsoft Office 2010 and later files (XLSM, XLTX, XLTM, XLSB, XLAM, XLSX) with
infections gets updated by replacing the infection with replacement text. However, Office
tools reports the recovery error message when the output file is opened.
■ Infected Microsoft Office files do not get replaced with replacement file.
Files include - XLS, XLA, XLT, PPT, PPS, POT, DOC, and DOT.
■ Encrypted PDF file inside the container file such as ZIP or TAR cannot be replaced with a
replacement file.
As a result, the original infected file is returned back to Symantec Protection Engine client.
■ Replacement file that replaced the Infected file cannot be renamed.
For example, the replacement file that replaced infected file eicar.com cannot be renamed
to DELETED.txt. File name remains as eicar.com and contains a notification text.