LiveZilla Live Help

You are here

SafeSquid for Windows SWG.2015.0209.2303.2 Released

The changes in SafeSquid Windows SWG 2015.0209.2303.2 are big enough to qualify it as a MAJOR release.
The Legacy subscription system has been completely re-built to introduce 4 different types of subscription mechanisms.


  1.  SafeSquid SWG for Windows now supports 4 different subscription mechanisms.
     1)  CPU time based subscription.
     2)  Concurrent connections based subscription.
     3)  Concurrent users based subscription.
     4)  Named users based subscription.
  2.  SafeSquid uses Service ID to uniquely identify SafeSquid instances from subscription service.
  3.  Legacy subscription system has been completely re-built, providing easy adaptability and  implemented facilities to:
     1)  Use same activation key, same encrypted passwords and same configuration on multiple instances.
          Now user can easily deploy SafeSquid on clusters and master slave configuration.
     2)  Identify SafeSquid instances from subscription server.
     3)  Limit the usage of SafeSquid instances from subscription server.
     4)  Share all types of subscription with multiple SafeSquid instances.
     5)  Activate / Deactivate SafeSquid instance from subscription server.
  4.  SafeSquid will use file as activation key. Activation key will be used to provide client instance identification to subscription server.
  5.  Added new upload file page on interface for uploading files to SafeSquid server.
     Using upload file page users can easily upload kerberos keytabs and other files to SafeSquid server.
  6.  SafeSquid will use RSA 1024 bit asymmetric encryption (earlier symmetric encryption was used) to encrypt passwords.
  7.  SafeSquid provides backward compatibility for earlier encryption technology. This will help users to use earlier config.xml. SafeSquid requires old activation key in place to decrypt earlier passwords.
  8.  Modified About page on interface to display subscription details.
  9.  Modified LDAP and SSL inspection sections to handle passwords encrypted with new technology.
  10.  Implemented facility to use profiles in combination with Access restrictions.
     This feature allows you to bypass authentication for specific sites.
  11.  Extended log parameters separated uniquely with tab (\t).
     This helps log parsers to generate reports using extended logs without any parsing issues.
  12.  Implemented authentication fail over. If NTLM / Negotiate authentication fails then SafeSquid challenges clients with basic authentication.

Increased Tolerance

  1.  SafeSquid now uses SHA2 hash algorithm to sign SSL certificates.
     SafeSquid was using SHA1 hash algorithm to sign SSL certificates.
     Some applications disabled SHA1 hash algorithm due to collision attacks, which causes problems.
     The problem manifests on Google chrome browser.


Bug Fixes

  1.  Bug Fix for matching of requests based on protocol.
  2.  Fixed SSCORE and SVSCAN stats messages display.
  3.  Critical bug fix in SSL inspection Section.
     A bug was discovered that caused SafeSquid to simply crash when user try to access sites which do not have registered domain names. For example sites like https://localhost:8989/ causes problems.


The Link for SafeSquid for Windows SWG.2015.0209.2303.2 is-