Sophos Anti-Virus for Linux release notes ----------------------------------------- Contents -------- Version numbers New in this version Known problems Additional information Information from previous versions Technical support Copyright Version numbers --------------- Sophos Anti-Virus : 6.4.5 Threat detection engine : 2.82.1 Threat data : 4.37, January 2009 New in this version ------------------- * The threat detection engine and threat data have been updated. Known problems -------------- * Parameters not set unless you include operator "set" (DEF 19553) If you use the command savconfig to set the value of a parameter, the value is not set unless you include the operator "set". For example, type: /opt/sophos-av/bin/savconfig set ScanArchives enabled * Desktop pop-up alerts not displayed on Red Hat version 5 64 bit (DEF 18916) On Red Hat version 5 64 bit, desktop pop-up alerts are not displayed. To fix this problem, install libXpm-3.5.5-3.i386.rpm. This file is needed by desktop pop-up alerts but is not installed by default by Red Hat 5. * End-User Licence Agreement display on Red Hat 2.1 with ja_JP.eucJP encoding (CR 24512) Due to a limitation of the more utility, the End-User Licence Agreement cannot display correctly in Japanese on Red Hat 2.1 computers that are using ja_JP.eucJP encoding. In such cases, the agreement is displayed in English. You can also see the copy on the Sophos website: www.sophos.com/legal/eula.html. * On-demand scanner requires new session in order to work if RPM distribution package is used for installation (CR 26892) If Sophos Anti-Virus is installed using the RPM distribution package that is created by mkinstpkg.sh, the on-demand scanner (savscan) requires a new session to be invoked before it will work. * Parameters based on file type do not work with newer version of libmagic (CR 23881) Configuration parameters that are based on file type do not work on distributions that use the newer libmagic 4.17, such as Ubuntu 6.10, SUSE Enterprise 10, and SUSE 10.2 and later. The following parameters are based on file type: ExcludeFilesLike AllowIfCorrupt AllowIfEncrypted AllowIfMultiVolumeArchive ExcludeFileOnType * Desktop pop-up alerts not displayed correctly on Asianux when using unsupported locale (CR 21865) 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. Additional information ---------------------- Some descriptions include the relevant identifier in brackets. You can use this if you need to contact Sophos technical support. * 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 distribution 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. * mkinstpkg.sh restricts choice of http port for Sophos Anti-Virus GUI If you run mkinstpkg.sh on a computer on which the Sophos Anti-Virus GUI is running, the script doesn't allow you to select the standard http port for the GUI. To work around this, disable the GUI before you run mkinstpkg.sh, as follows: /etc/init.d/sav-web stop * Remote Management Service doesn't start if Sophos Anti-Virus has been installed from NFS filesystem If you install Sophos Anti-Virus from an NFS filesystem, the Remote Management Service won't start. To work around this, use an alternative installation source instead, for example a Samba share. Information from previous versions ---------------------------------- 6.4.4 * This version includes fixes for the following problems: (DEF 27700) On SUSE Linux Enterprise Server version 8, if you try to install Sophos Anti-Virus so that it is managed by Sophos Enterprise Console, the Sophos management agent is unable to report anything to Enterprise Console. (DEF 27270) If an EVENT_APP_EXCEPTION_RAISED error is logged to the Sophos Anti-Virus log, the error message is not displayed correctly. 6.4.3 * This version includes fixes for the following problems: (DEF 25370) On computers that are running in a German locale, the email alert timestamps are one hour different to the operating system time. (DEF 26012) If you abort a scan by pressing CTRL+C, the message in the Sophos Anti-Virus log is "On-demand scan finished" instead of "Scan aborted by user". (DEF 25987) If Sophos Anti-Virus fails to update from the primary update source but does update from the secondary update source, syslog shows that it failed to update at all. (DEF 27139) If on-access scanning is disabled, Sophos Anti-Virus doesn't report to Sophos Enterprise Console that it has been updated with new IDEs. (DEF 26420) Sophos Anti-Virus doesn't correctly handle exclusions that end with an asterisk. (DEF 25666) If the Sophos Enterprise Console updating policy that is used by a Linux computer is reset to factory defaults, Sophos Anti-Virus successfully updates using the previous updating policy. 6.4.2 * The Sophos kernel interface module (Talpa) has been updated to version 1.6.1. * (DEF 23243) Talpa can now compile on kernel version 2.6.16.54-0.2.5-xen and later. Technical support ----------------- For technical support, visit www.sophos.com/support. If you contact technical support, provide as much information as possible, including the following: * Sophos software version number(s) * Operating system(s) and patch level(s) * The exact text of any error messages Copyright --------- Copyright © 2007-2009 Sophos Group. 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 Plc and Sophos Group. All other product and company names mentioned are trademarks or registered trademarks of their respective owners.