This is the first development release of E2Guardian V4.

V4 is written in C++11 and uses threads, in order to make e2guardian scaleable to very large systems.

This version is largely backward compatible with v3 configuration files.

Testing is showing an increase in speed and a big reduction in memory usage, as well as almost instant gentle restart with no interruption to service.

Please see notes/NEWIN_v4 for details, before trying to configure or compile.

This release fixes a number of issues with v3.4.0 and has updated documentation.

This release is now regarded as stable
Only required bug and security fixes will be applied in the v3.4.x point releases.

If you are upgrading from a previous e2guardian major release you may need to alter your
config files. If you are upgrading from dansguardian you will have to change your
config files in order to make a working system.

See e2guardian.release and the example configuration files for details.

If you are implementing SSL MITM please read the updated notes/ssl_mitm

E2Guardian 3.4.0 (released this on 29 Jan)

The latest release of E2guardian, version 3.4.0, has just been released.

This release is a major version resolving several issues found in the prior E2guardian releases.

This release is now regarded as stable
Only required bug and security fixes will be applied in the v3.4.x point releases.

Big thanks to Philip Pearce for his great work, many fixes and enhancements specially about SSLMITM

Some things to be aware of :

• createlistcachefiles now defaults to off (Considered like useless)
• new sslsiteregexplist added (optional)
• new option textmimetypes (eg: Filtering content of JavaScript and JSON )
• search term logic changed so banned_search_override works with both search block list and with weighted search term.
• SSLMITM Upgrade sha1 to sha256
• new namesuffix option - one log file by instance (syslog) -

And more ...

Summary of changes in this release (v3.4.0) can be found in e2guardian.release

You are invited to upgrade to this release as soon as possible, but read the config sample files before !
You can find the bugs fixes description here
https://github.com/e2guardian/e2guardian/issues

The latest release of E2guardian, version 3.2.0, has just been released.

This release is a major version resolving several issues found in the
prior E2guardian releases.

This release is now regarded as stable

Only required bug and security fixes will be applied in the v3.2.x point releases.

Some changes to be aware of:

• SSLIMITM is now fully functional in explicit proxy mode
• All the filtering options are migrated to the e2guardianfx.conf file(s), e2guardian.conf is now completely dedicated to the engine (timeout values, log format, AV engine, etc)
• Maxuploadsize option removed as no longer used with e2guardian.conf
• generatedlinkpath option removed as no longer used
• monitorhelper option added - path of monitor helper script - allows feedback when system available and when cache not working
• xforwardedforfilterip option added - restricts xforwardedfor to specified ip(s)
• Improved performance during gentle restart
• New feedback options for use with loadbalancers

And more ...

Summary of changes in this release (v3.2.0) can be found in
e2guardian.release

You are invited to upgrade to this release as soon as possible, but read
the config sample files before !
You can find the bugs fixes description here
https://github.com/e2guardian/e2guardian/issues

It is an interim release to address the retirement of the Google nosslsearch feature in January 2015

Issues have been found with certificate checking on some platforms, so in order to provide a solution, certificate checking is disabled in this release. Provided MITM is restricted to Google sites by using the onlymitmsslgrey option, the lack of certificate checking will not be a problem.

For more details on setting up MITM see notes/ssl_mitm

Download: Here