

Sophos SAV Dynamic Interface version 2.6.0 release notes
------------------------------------------------------


Contents
--------

About these release notes
Fixed issues
Information from previous releases
Known issues
Technical support
Legal notices


About these release notes
-------------------------

These are the release notes for the SAV Dynamic Interface package for Windows
and UNIX computers.


Fixed issues
------------

* Added a new configuration option for ICAP and SSSP allowing
  the True File Type reporting of the scanned file.
  
* (Linux only) The dependency on shared library libssp has been removed.

* (Linux only) There are two 32-bit packages, savdi-linux.intel.libc6.glibc.2.3.tar and 
  savdi-linux.intel.libc6.glibc.2.2.tar, the latter provided for systems which cannot 
  use the former.
  
* (Linux only) There are two 64-bit packages, savdi-linux.amd64.glibc.2.3.tar and
  savdi-linux.amd64.glibc.2.3.ssp.tar. The latter build includes stack smashing 
  protection. The former build is provided for systems which do not have the stack
  smashing support functions in glibc.

* (Linux only) Fixed a bug. When SAV Dynamic Interface ran on a system on which
  Sophos Anti-Virus on-access scanning was active, SAVDI leaked a handle for
  each file it scanned, eventually reporting "too many open files" on attempts
  to scan a file.


Information from previous releases
----------------------------------

Version 2.5.0

* (ICAP) Added a new mode for ICAP allowing the use of the ICAP statuses
  204 and 200 to be used to indicate a clean and not clean results 
  respectively. 

* (*nix only) Fixed a bug that caused child processes to crash on 32 bit
  Linux systems.

* Fixed a bug that caused the sample application, icap.pl, to incorrectly 
  handle file paths containing a '-'.


Version 2.4.0

* The location of the language file is now configurable with a –m command line option.

* (*nix only) Installing SAVDI to a custom location could fail on a 64 bit system.

* New configuration option to output long detection name.

* Added new SAVDI sample-apps: 
	- savi.py – A simple Python module using SSSP
	- savitest.py – To illustrate the use of savi.py above
	- sssp.c – A  simple SSSP client in C
	- SAVDIClient.java  –  a simple Java client using SSSP

* Long HTTP header lines could cause an '500 Server Error’ to be returned.

* (Windows only) SAVDI could prevent Windows SAV updating its drivers.

* (*nix only) SAVDI could fail to install properly on non-English locales.

* Running out of temporary disk space could result in SAVDI failing.

* Solaris 11 (sparc) is supported.

* An exception in the virus engine could cause SAVDI to fail.


Version 2.3.0

* (*nix 64bit only) The install script would fail to find the SAV directories
  containing the engine and virusdata. The install script will in addition
  create a configuration file containg the discovered directories

* (*nix 32 bit only) Files of a size greater than 2GB were rejected as non-existent.

* (Windows only) The messages that are logged when an engine update has been 
  detected have been made more explanatory and relevant.

* (ICAP) The retain: ALL option did not work.

* (ICAP) The virus data version has been added to the ISTag. The engine and virus 
  data version details have been added to the response to the OPTIONS request.

* (SSSP) Incorrect SSSP commands are rejected with a REJ response but are not logged.
  All REJ responses will now cause a log entry.

* (SSSP) The engine and virus data version details have been added to the response 
  to the QUERY ENGINE request.

* When a new log file was started, the old log file was held open.

* A SAVI option that should be set last was incorrectly being set too early.


Version 2.2.0

* ICAP will tolerate a trailing '/' on the service name.

* The reporting of virus data load errors has been improved

* Log file handling has been changed so that if SAVDI is unable to write to
  the log file it will revert to a backup log. In daemon or service mode
  this will be the syslog or event log depending on the OS. If that fails,
  SAVDI will continue and not exit.

* If SAVDI is unable to create a temporary file, it will attempt to create
  one in the systems standard temporary directory instead. If that fails, it
  will fail the scan request and SAVDI will continue and not exit.

* (*nix only) Internal improvements to signal handling and logging that
  could result in a deadlock or hang.


Version 2.1.1 (Windows only release)

* (Windows only) SAVDI service was failing to exit appropriately
  to be restarted by the SCM.

Version 2.1.0

* The second line of the ICAP header is ignored. Depending on the order of the
  ICAP headers, this may result in failure to complete the request.

* %XX sequences in HTTP headers that are included in an ICAP request are
  incorrectly decoded. This results in failure of the request.

* On Windows, SAVDI/SSSP and SAVDI/SOPHIE are not fully impersonating the
  client. This results in VMWare VMDK files that are mounted as volumes being
  inaccessible.

Version 2.0

* An implementation of the ICAP standard has been added to SAVDI.


Known issues
------------
* (Solaris) A missing configuration file will, correctly, prevent SAVDI from
  starting. On Solaris, this may cause SAVDI to crash instead of reporting the
  error and exiting cleanly.

* File paths of a length greater than MAX_PATH characters will be rejected.

* (Windows, *nix 32bit) SSSP/SCANDATA will reject data of more than 2GB. *nix
  64bit is unaffected.

* In the SOPHIE protocol, a maxscandata configuration value of 0 does not mean
  unlimited, but maximum size zero.


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/support/

* Download the product documentation at http://www.sophos.com/support/docs/

* Open a ticket with our support team at 
     https://secure2.sophos.com/support/contact-support/support-query.aspx


Legal notices
-------------

Copyright © 2017 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.
