Sophos Anti-Virus for Linux release notes ----------------------------------------- Contents -------- Version numbers New in this release Fixed issues Known issues Additional information Information from previous releases Technical support Legal notices Version numbers --------------- Sophos Anti-Virus : 9.2.1 Threat detection engine : 3.43.0 Threat data : 4.89, May 2013 New in this release ------------------- * Native 64-bit support. Installation on 64-bit versions of Linux is now possible without the use of 32-bit compatibility libraries. * The third-party libraries have been updated. * The threat detection engine and threat data have been updated. * Sophos Anti-Virus 9.2.1 is not compatible with the following operating systems: * SUSE Linux Enterprise Server (SLES) 9 For more information, see http://www.sophos.com/en-us/support/knowledgebase/119218.aspx. * TurboLinux 10 For more information, see http://www.sophos.com/en-us/support/knowledgebase/119219.aspx. For continued support on these platforms continue using Sophos Anti-Virus version 7.x. To prevent automatic upgrade to version 9, you must manually select the "7 Extended Maintenance Recommended" Sophos Update Manager software subscription. For more information, refer to the knowledgebase articles mentioned above. Please note that support for both of these platforms will be withdrawn completely in 2013. For more information about product and platform retirement, see http://www.sophos.com/en-us/support/knowledgebase/119114.aspx. Fixed issues ------------ * (DEF84244) Named scan logs report scan errors by ID only and do not include the error message text. * (DEF87254) Sophos Anti-Virus excludes from a scheduled scan all files or folders if the beginning of their names matches a defined exclusion. For example, if you have three folders, test, test1, and test2, and configure Sophos Anti-Virus to exclude /test, all three folders will be excluded from a scheduled scan. Known issues ------------ * Desktop pop-up alerts not displayed on Red Hat Enterprise Linux version 6 (WKI67300) On Red Hat Enterprise Linux version 6, desktop pop-up alerts are not displayed. To fix this problem on 32-bit versions, install libXpm from the following package on the Red Hat installation DVD: * libXpm-3.5.8-2.el6.i686.rpm To fix this problem on 64-bit versions, install libXau, libxcb, libX11, and libXpm from the following packages on the Red Hat installation DVD: * libXau-1.0.5-1.el6.i686.rpm * libxcb-1.5-1.el6.i686.rpm * libX11-1.3-2.el6.i686.rpm * libXpm-3.5.8-2.el6.i686.rpm These packages are needed by desktop pop-up alerts but are not installed by default by Red Hat. * Desktop pop-up alerts not displayed on Red Hat Enterprise Linux version 5 64 bit (DEF18916) On Red Hat Enterprise Linux version 5 64 bit, desktop pop-up alerts are not displayed. To fix this problem, install libXpm from the following package on the Red Hat installation DVD: libXpm-3.5.5-3.i386.rpm This package is needed by desktop pop-up alerts but is not installed by default by Red Hat. * Desktop pop-up alerts not displayed correctly on Asianux when using unsupported locale (DEF11871) Desktop pop-up alerts in unsupported locales (zh_CN.UTF-8: Traditional Chinese and Korean) on Japanese installations of Asianux are displayed using identifiers (for example, VIRUS_FOUND_IN_FILE_ACCESS_DENIED) rather than the corresponding English text. * Local configuration is replaced with Enterprise Console configuration during the upgrade When you upgrade to Sophos Anti-Virus 9 on a computer that is managed by Sophos Enterprise Console (SEC) and is configured locally (differs from the SEC policy), the locally configured settings are overwritten by the SEC configuration. However, local configuration that cannot be configured from SEC will not change. * Enterprise Console does not show that a file has been quarantined (DEF74349) On a Sophos Anti-Virus installation that is managed by Sophos Enterprise Console, if an on-demand scan quarantines a file, savlog shows that the file has been quarantined, but in Enterprise Console, "action taken" is blank. * syslog does not show that a file has been disinfected (SUG74393) If on-access scanning disinfects a file, savlog shows that the file has been disinfected, but the entry in syslog omits the text "The file has been disinfected." Additional information ---------------------- * Sophos Anti-Virus and PureMessage for UNIX If you install Sophos Anti-Virus on a mail server that is running Sophos PureMessage for UNIX, you must make sure that scanning of MIME files is disabled in Sophos Anti-Virus. This is because scanning MIME files with Sophos Anti-Virus might prevent PureMessage from accessing files that contain viruses. By default, MIME scanning is disabled. * Installation in non-UTF-8 and non-ASCII encoded locations You can't install Sophos Anti-Virus in a location that is specified by a non-UTF-8 and non-ASCII path. * Installation on computers using non-UTF-8 and non-ASCII encoding On a computer that is using non-UTF-8 and non-ASCII encoding, to install from the deployment package that is created by mkinstpkg.sh, run the installation script as follows: LANG=C ./sophos-av/install.sh * Japanese language support Sophos Anti-Virus can be installed on computers that are using ja_JP.eucJP and ja_JP.UTF8. Installation on computers with ja_JP.sjis locale (Japanese with Shift-JIS encoding) is not supported. * Sophos Remote Management System doesn't start if Sophos Anti-Virus has been installed from NFS filesystem If you install Sophos Anti-Virus from an NFS filesystem, Sophos Remote Management System won't start. To work around this, use an alternative installation source instead, for example a Samba share. Information from previous releases ---------------------------------- March 2013 New in this release * The threat detection engine and threat data have been updated. Fixed issues None. February 2013 New in this release * The threat detection engine and threat data have been updated. Fixed issues * Installation fails on unsupported distros - manifest.spec error (DEF87029) When installing on an unsupported distribution using a standalone installer, if on-access scanning is enabled during the installation, the following error occurs: ***Unable to copy /tmp/sophos_distribution_fQCa8iw/sophos-av/sav-linux/ manifest.spec to /opt/sophos-av/update/manifest.spec: no such file or directory terminated install [Errno 2] no such file or directory: '/tmp/sophos_distribution_fQCa8iw/ sophos-av/sav-linux/manifest.spec' The installation is now corrupt and savupdate will not complete due to: "/opt/sophos-av' already exists and isn't a valid installation directory." * savd core dumps after an upgrade to Sophos Anti-Virus 9 (WKI86726) After upgrading to Sophos Anti-Virus 9.0.0, intermittent savd core dumps occur if no DNS servers are present on the network. January 2013 New in this release * The threat detection engine and threat data have been updated. Fixed issues None. Technical support ----------------- You can find technical support for Sophos products in any of these ways: * Visit the SophosTalk forum at http://community.sophos.com/ and search for other users who are experiencing the same problem. * Visit the Sophos support knowledgebase at http://www.sophos.com/en-us/support.aspx * Download the product documentation at http://www.sophos.com/en-us/support/documentation.aspx * Send an email to support@sophos.com, including your Sophos software version number(s), operating system(s) and patch level(s), and the text of any error messages. Legal notices ------------- Copyright (c) 2007-2013 Sophos Limited. All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording or otherwise unless you are either a valid licensee where the documentation can be reproduced in accordance with the licence terms or you otherwise have the prior permission in writing of the copyright owner. Sophos and Sophos Anti-Virus are registered trademarks of Sophos Limited. All other product and company names mentioned are trademarks or registered trademarks of their respective owners.