LiveZilla Live Help

You are here

Revision History - Linux

SafeSquid for Linux SWG.2015.0312.1900.3 Released

Fixed memory leak in Kerberos authentication, Subscription update and SSL inspection process. Removed SSO authentication latency.

SafeSquid for Linux SWG.2015.0221.1650.3 Released

Improved support for LDAP environments with over 5000 users. Extended logs are now easier to parse.

SafeSquid for Linux SWG.2015.0115.1830.3 Released

Introduced Failover for Kerberos Authenticaction and display upload activation key form on WebUI, if Activation Key is not activated.

SafeSquid for Linux SWG.2014.1231.1551.3 Released

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

SafeSquid for Linux SWG.2014.1218.1529.3 Released

Increased Tolerance for signing SSL certificates, now uses SHA2 hash algorithm. Bugfix for sites which do not have registered domain names.

SafeSquid for Linux SWG.2014.1212.1224.3 Released

Increased Tolerance for kerberos Authentication & LDAP connections. Bugfix for buffer overflow, FTP directories with spaces & accounting connections handled.

SafeSquid for Linux SWG.2014.1127.1148.3 Released

Improved categorization of website based on the content provided by website and bug-fix in SSCORE module.


SafeSquid for Linux NTLM.RC. Released

Improved handling of HTTP headers, URLs upto 16385 characters, URLs having UTF-8 characters, Directory services with more than 500 users.

SafeSquid ntlm-RC4.3.8.7

About SafeSquid ntlm-RC4.3.8.7


  • Improved support for non-browser web-clients:
    • SafeSquid now facilitates connection persistence for client applications that may not include proxy-connection / connection headers.
    • SafeSquid now supports automatic transmission of connection-encoding headers depending upon client request headers.
  • Speed enhancements to further improve the throughput speed.
  • Optimized System Resource Utilization.
    • SafeSquid now uses a single thread to close idle client connections, in pool.
    • SafeSquid now uses maximum CPU resources for transferring data.
    • Optimized memory utilization.
  • Improved handling of web-server redirect responses that may not have included connection-close headers, when not indicating the content-length or transfer-encoding.
  • The safesquid logo is now embedded in the UI pages and templates as base64 encoded image preventing additional request from the client to display logo.

SafeSquid-2013.0617.2130.3 Patch

Minor enhancement for RFC violating response headers from some web-servers.
Some web-servers like respond with a 301 redirect response headers.
These headers do not contain the entity as mandated by RFC 2616.
SafeSquid now enforces a proper conversion of these headers.
The Links to the Patch are-
1. SafeSquid 32- Bit Versions

2. SafeSquid 64- Bit Versions

Patch Can be applied using following steps-
Step 1# Do Save Setting from Safesquid Interface and Take Backup of config.xml

  • cp /opt/safesquid/safesquid/config.xml /config.xml-bakcup-$(date +%F)

Step 2# Extract Download file and cd into latest Safesquid

  • tar -xzvf safesquid_latest.tar.gz
    cd safesquid

Step 3# Actual Upgrade Steps

  • /etc/init.d/monit stop; /etc/init.d/safesquid stop; ./ ; /etc/init.d/safesquid start ; /etc/init.d/monit start;

Note: - if you are not using monit then just use below command

  • /etc/init.d/safesquid stop; ./ ; /etc/init.d/safesquid start

If you are using SafeSquid for the first time you can follow SafeSquid Installation Steps.