LiveZilla Live Help

You are here

Revision History - Windows

SafeSquid for Windows SWG.2015.0730.1621.2 Released

Identified and fixed a bug which caused SafeSquid to simply close some connections unconditionally.

SafeSquid for Windows SWG.2015.0509.1500.2 Released

Implemented LDAP page control search, improved SSL inspection performance, update process of Virus signatures and Website classification database.

SafeSquid for Windows SWG.2015.0209.2303.2 Released

Introduced CPU time, Concurrent connections, Concurrent users & Named users subscription types. 1024 bit RSA encryption of passwords.

SafeSquid for Windows 2013.0619.1831.2 patch

Added missing image-filter DLLs and flags to check POSTDATA from the client, before sending response for authentication / blocking request.

SafeSquid for Windows 2013.0612.2050.2 patch

Bugfixed authentication process and added missing DLL named bgd.dll.

SafeSquid for Windows 2012.1208.1905.2-20121208 patch

Bugfix for a vulnerability that caused SafeSquid to terminate abnormally.
In certain cases during SSO authentication SafeSquid crashed, the problem has been resolved in the patch.

Pre-Requirements: Safesquid Business installed

Steps to install patch-

SafeSquid for Windows (Updated)

Critical Security BugFix:
The HTTP response header lines are in the usual text header format, which is: one line per header, of the form "Header-Name: value", ending with CRLF.
SafeSquid failed to correctly parse headers when the number of spaces or tabs between the ":" and the value was more than one.
One of the immediate mal-effects of this was non-detection of "Transfer-Encoding: chunked" headers.
This was largely witnessed with Microsoft IIS/6.0 webservers.

SafeSquid for Windows

  • Reduced CPU utilization.
  • Faster loading of dynamic pages.


SafeSquid for Windows

SafeSquid now offers better support for FTP over HTTP. A new built-in template handles user authentication for FTP sites that require user authentication. Reduced latency and overall response times.Security Bugfix to prevent faulty bypassing of content analysis of requests. Improved tolerance to slow response from heavily loaded, slow responding web-sites. Major improvements in ICAP, now allows use of multiple ICAP services. SafeSquid connects to each ICAP server in the list, until one modifies the request or response.