Print 

E2guardian 5.1.1 is out !

Written by Frédéric Bourgeois on .

We are proud to announce the availability of the V5 (V5.1.1) release.
As usual now this is essentially the work of Phillip, a mammoth task (certainly from one of the labours of Hercule).

Many, many thanks to all those who have tested, bug-checked and provided improvement suggestions for this new version. As a result, this is the most stable and scale-able release to date.

This new 5 series of e2guardian brings new features and changes providing improved performance over earlier release series.

Main new features:

  • https transparent filtering
  • ICAP server mode
  • upstream proxy now optional
  • rebuilt flexible filtering engine

This version is not backward compatible with v4 configuration files. Please study example configuration files and lists.

Please see notes/NEWIN_v5 and INSTALL for details, before trying to configure or compile.

Please tag bug reports with 'V5.1.1' and If your issue is an implementation question, please ask your question on https://groups.google.com/forum/#!forum/e2guardian

Please don't use Github Issues to ask for help !

Developers please pull branch v5.1 for this release, v5develop will be used for future enhancements.
In configs directory you can find a Dockerfile that helps you to create a Docker image and container.

I made a package for Debian Jessie, but it's an deprecated OS for us (as Ubuntu 16.04), please migrate to Stretch or 18.04.

https://github.com/e2guardian/e2guardian/releases/tag/V5.1.1

 Print 

New e2guardian stable version 4.1.4 released

Written by Philip Pearce on .

This release fixes a number of issues with v4.1.3 and has updated documentation.

This release is now regarded as stable
Only required bug and security fixes will be applied in the v4.1 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 the example configuration files for details.

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

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?q=is%3Aissue+is%3Aclosed

Summary of changes in this release can be found in Changelog

 Print 

WIki is out !

Written by Frédéric Bourgeois on .

This wiki is maintained by Spike and the rest of the team

How I can contribute ?

-   Promote the site and e2guardian — Tell others about the site to drive traffic to the wiki.
-   Create new content — New tutorials and articles are always welcome, and help the wiki to keep growing you can also cleanup existing pages.
-   Post on the forum — When somebody posts on the forum asking for help, you should try to help them to the best of your abilities.

 

Before sending a ticket to github, think on how you can contribute positively to the discussions. It is easy to subscribe or unsubscribe from our forum

https://groups.google.com/forum/#!forum/e2guardian

 

 

 

 Print 

E2guardian first v4 Stable Release - version 4.1.0

Written by Frédéric Bourgeois on .

This is first stable release of E2Guardian V4.

Only required bug and security fixes will be applied in the v4.1.x point releases.

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

This version (v4.0 dev & v4.1 stable) 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 list reload with no interruption to service.

A big thanks to everyone who has contributed to getting this new release production-ready in such a short time.

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

 Print 

E2Guardian 3.5.1

Written by Frédéric Bourgeois on .

This release fixes a number of issues with v3.5.0
This release is now regarded as stable

For developer Eguardian 3.5.x series became DEPRECATED, please try and report only from V4

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

More Articles...