SafeSquid
SafeSquid is a content filtering proxy server. It supports 'profiled' Internet access, a browser based interface, very fast throughput, DNS caching, content caching, pre-fetching, bandwidth control, virus scanning, ICP, CARP, and ICAP clients, source, target, and time-based granular firewall style rules to allow or deny content like music, videos, Flash and Java applets, messengers, chats, cookies, ActiveX, scripts, etc., remote authentication, real-time text and image analysis for blocking pornography, and an URL filter.
| Tags | Networking Security Firewalls Internet Web HTTP Servers Proxy Servers |
|---|---|
| Operating Systems | POSIX Linux |
Recent releases
- 21 May 2009 07:45
Changes: SafeSquid now allows complete TCP tuning. Content caching now takes preventive action when the caching parameters are ill configured. Optimizations have been introduced to allow use of libhoard. The init script has also been optimized for invoking libkeepalive. Data transferred in the CONNECT requests is now recorded in both Access and Extended Logs. The linking mechanism to the libgmp library has been modified. The algorithm for detecting the DDoS attacks was modified. Behavior of timeout directives in the general section was modified.
- 13 Feb 2009 18:28
Changes: Improved mechanisms for addressing CLOSE_WAIT related problems. This release can reclaim both half-open and half-closed sockets (CLOSE_WAIT state connections) and reuse them for both inbound and outbound connections. A logical flaw that caused a memory leak on application of profiles under certain conditions is fixed. The cProfiles feature has been enhanced for speed. Depending upon user configuration, resolution speed will be about 30 to 70% faster. The init script has been improved, and a few more parameters have been made tunable via startup.conf.
- 29 Dec 2008 18:50
Changes: This release has moved to the higher GLIBC that allows optimal use of CPU. It has improved the THREAD_TIMEOUT and SOCKET_TIMEOUT parameters to allow reduction of CLOSE_WAIT and give better response to Piplining enabled clients and load-balancers. Many minor improvements that increase throughput and speed. The application of prefetching rules is now logged in the native log. A bug that broke the QoS control feature of User Limits has been traced and fixed.
- 20 Nov 2008 09:12
Changes: A new parameter, OVERLOAD_FACTOR, has been introduced. A logical flaw in cache cleaning operation has been traced and fixed. A logical flaw in logged cache object size has been traced and fixed. The design of cProfiles has been modified to allow it to query for an almost unlimited number of Web sites simultaneously. Failure of the MD5 integrity check for cached objects has been corrected. A logical bug while updating or modifying the entries in cache has been corrected. Dynamically generated objects are not cached now. Memory requirements have been tremendously slimmed down.
- 31 Jul 2008 10:39
Changes: This release fixed bugs where SafeSquid failed to discard cached objects from memory for indefinite periods when the memory usage exceeds 100% and connections were not established when the network latency was more than 100ms.
- All comments
Recent commentsArrived! 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:
http://www.safesquid.com/html/viewtopic.php?p=9692
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