SafeSquid for Microsoft Windows verison 3.4.2 was released recently. SafeSquid for Windows now supports NTLM authentication (SSO) and Pornographic Image Filter. Refer to this link to know more able the latest release - http://www.safesquid.com/html/viewtopic.php?t=3634
SafeSquid for Windows 220.127.116.11 released:
SafeSquid for Windows 18.104.22.168 contains minor bugfixes, and important enhancements.
SafeSquid for Windows, both Personal Edition and Business Edition, now supports use on all Windows Platforms, including Windows 2003 / 2008 / Home Server / Vista / Windows 7.
SafeSquid for Windows now allows you to authenticate users on the Local System (LSA authentication) or on LDAP / AD. LDAP / AD usergroup mapping has been improved and allows you to create access polices based on the group a user belongs to on LDAP / AD. A newly designed LDAP Sub-System (LSS) allows you to connect to the specified AD / LDAP server and pre-fetches the Directory information of users, on startup.
The Access Restriction section has an option for enabling / disabling NTLM authentication, which is not active in this release. Work is in progress in this area, and you will be able to make use of this in the next release.
SafeSquid for Windows now detects any critical internal flaws, and creates a minidump file in the same folder that contains it's native logs. These dump files can be sent to the Technical support for analysis, for a quickly identifying the problem.
For more details, please refer to -
Arrived! SafeSquid for Microsoft Windows
The SafeSquid Team is so happy to bring SafeSquid to Microsoft Windows Platform.
The first line of editions in this series is named "SafeSquid Personal".
SafeSquid Personal has been natively built for Microsoft Windows based Operating Systems.
This distribution, however retains the functional architecture of SafeSquid for Linux.
SafeSquid Personal is free and has not time based expiry.
Please read more at:
Getting Ready for Version 4.2.1
For SafeSquid 4.2.1 we are focusing on improvisations in logs, and handling of forwarded requests.
# Until SafeSquid 4.2.0 SafeSquid needed a restart when the logfiles reached 2GB size. From 4.2.1 this limitation will be removed.
# The Native log will now record the application of "profiles".
# A unique record identifier will now be printed with every line of extended log, to prevent duplication of records when imported into SQL databases.
# Prior to 4.2.1, the time spent by the user on an HTTPS / SSL session was not recorded in the Access Log. From 4.2.1 the CONNECT requests will be appropriately logged.
# New variables for use in Custom Templates and External Parsers, are being introduced.
For details see http://www.safesquid.com/html/viewtopic.php?p=8007#8007
An open, cross-platform journaling program.
A scientific plotting package.