Sophos Anti-Virus for Linux release notes

Version numbers

Sophos Anti-Virus 7.6.7
Threat detection engine 3.47.1
Threat data 4.93, September 2013
Note: We did not release Sophos Anti-Virus in August 2013 because we wanted to enhance the product's resilience.

What's new

This section lists new features and updates included in the last four monthly releases of Sophos Anti-Virus for Linux 7.

To view the list of issues fixed in these releases, see Fixed and known issues

New in this release

  • The threat detection engine and threat data have been updated.

New in 7.6.5, July 2013

  • The threat detection engine and threat data have been updated.

New in 7.6.4, June 2013

  • The threat data have been updated.

Fixed and known issues

This section lists issues fixed in the last four monthly releases of Sophos Anti-Virus and the known issues in this release.

Go to known issues

Known issues

Issue ID Description
DEF75307 Installer returns error if Talpa binary pack unavailable.

On some distributions, if you install Sophos Anti-Virus with on- access scanning turned off, the installer returns an error if no Talpa binary pack is available. To work around this issue, install Sophos Anti- Virus with on-access scanning turned on.

DEF74349 Enterprise Console does not show that a file has been quarantined.

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.

DEF74393 syslog does not show that a file has been disinfected.

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."

SUG67351 Installation fails on Red Hat Enterprise Linux version 6 64-bit.

On Red Hat Enterprise Linux version 6 64-bit, the following packages must be installed so that the installation of Sophos Anti-Virus succeeds:

  • glibc-2.11.1-1.i686
  • nss-softokn-freebl i686 3.12.4-10.fc12
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.

DEF19553 Parameters not set unless you include operator "set".

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>
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.

CR24512 Licence Agreement not displayed correctly in Japanese on Red Hat 2.1.

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/en-us/legal/sophos-end-user-license-agreement.aspx

CR26892 On-demand scanner requires new session in order to work if RPM distribution package is used for installation.

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.

CR23881 Parameters based on file type do not work with newer version of libmagic.

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
DEF11871 Desktop pop-up alerts not displayed correctly on Asianux when using unsupported locale.

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 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.

Technical support

You can find technical support for Sophos products in any of these ways:

Legal notices

Copyright © 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 license terms or you otherwise have the prior permission in writing of the copyright owner.

Sophos, Sophos Anti-Virus and SafeGuard are registered trademarks of Sophos Limited, Sophos Group and Utimaco Safeware AG, as applicable. All other product and company names mentioned are trademarks or registered trademarks of their respective owners.