CENSORBLOX
The CensorBlox system was previously built from highly configured squid proxy server and some nifty scripting and cron jobs to automate the whole process. We are now working on delivering a Windows version to coincide with our Linux based. The end product is a system that delivers a web filter without costing thousands of dollars. Custom configurations can be applied on top of the system if a site has particular blocking or unblocking requirements.
After being utilised in a number of Victoria Schools with great effect and being used in businesses across Victoria and Queensland, We have decided to publish some basics and some of the CensorBlox details for persons still running the system and for others that would like to use our systems or parts there of.
HISTORY;
Censorblox started out as a very basic web filter for primary schools that I worked in, after I had walked into many classrooms were students were accessing websites that they should not be accessing. Discussions with teachers where their main inquiry being “How come the students can get to that content?”. After investigating the ability to use open source software on top of a Linux server the first test system was put together and named “FilterBox”.
FilterBox (Ver.1) consisted of a Fedora Linux Install with Squid, Apache, Webmin and a few other pieces to tie it together. It was a very basic system with Black, Grey and White control lists.
- Black control list – sites and ip addresses were blocked fully no visits and no downloads
- Grey control list – sites and ip addresses were blocked from downloading content but could be browsed for information
- White control list – sites and ip addresses were fully allowed, content could also be downloaded
- Updates were manually installed & configuration was down by hand
- Time consuming for administration
CensorBlox (Ver.2) consisted of a Fedora Linux Install with Squid, Apache, Webmin and a lot of other pieces to tie it together. This was an evolved FilterBox with automated updates and configurations.
- Local Site Black control list – sites and ip addresses were blocked fully no visits and no downloads
- Local Site Grey control list – sites and ip addresses were blocked from downloading content but could be browsed for information
- Local Site White control list – sites and ip addresses were fully allowed, content could also be downloaded
- Master control lists
- Categorised control lists
- Automated updates
- Automated configuration archives
- Quicker installs
- Less administration
- More of the product pushed back into the backend servers at the datacenter
2010: Public release of parts of CensorBlox, web based proxy server component seperated out for those who only want to control web proxies.
Windows version research and release.
2009: Research into virtual appliance, further development to the whole system.
2008: Further research into using Windows server, IIS and DNS server as filtering system. Backend server relocation.
2007: System overhaul to handle larger amounts of traffic and throughput.
2006: Addition Categories added, configurations and backend upgraded.
2005: Research on a Microsoft based system for persons using that operating system, implemented ISA server basic blocking and updating
2004: Web based proxy server filtering investigated and added, Secondary school configurations setup and enhanced
2003: Backend server upgraded in order to search out and spider unknown websites. Link Directory installed and used by primary schools.
2002: Name change from FilterBox to CensorBlox, addition features added. Auto submitted urls for blocked sites and any false positives.
2000: Backend server developed to handle submissions & url database, automatic nightly updating and configuration archiving.
1998: Original design, testing and implementation of FilterBox (Linux support only)
