E2guardian package for pfsense - $??

Mobile_Bob

I see that postfix was denied… My guess is he is out... I HOPE not, but... Someone else may have to take over the package. I'm a little disappointed since many people including myself donated money toward this package. I could understand if e2guardian was also denied, but as far as I know it's still just incomplete.

It's also possible that PFSense would deny this package as well. It's not as cumbersome as postfix is, but I don't know what direction they are moving since previously the postfix package was approved... :'(

pfsensation

This really would've been a big step forward for PfSense firewall, as web filtering goes. The standard SquidGuard is a nightmare. Really would've loved that HTTPS scanning :(

aGeekhere

for now just force google and bing into safe search

jetberrocal

Here is some summary to install the current e2guardian in psense:

1. Create a virtual machine with FreeBSD 10.3 or the same version of your pfsense's FreeBSD.
Make sure it has Internet access and connectivity to your pfsense machine

2. Fetch e2guardian from FreeBSD ports

pkg add http://pkg.freebsd.org/freebsd:10:x86:64/latest/All/e2guardian-3.4.0.3.txz

Fetching e2guardian-3.4.0.3.txz

3. Please have a look at https://www.freshports.org/www/e2guardian/ - by default SSL=off: by default- you need to switch it on.

portsnap fetch extract update && cd /usr/ports/www/e2guardian

make config

At this stage you need to check SSL to build e2g with SSL support or check other build options you need.

make install clean

4. Create package for personal use.

make package

But it says to run "portlint -CN" and that gives an error.
That portlint is only relevant if your developing a package yourself.
In this case your compiling an existing package and probably safe to ignore the portlint 'error' about to much files and cleanup to be done..

5. Copy the created package to your pfsense machine.
If your FreeBSD virtual machine does not have a web server then use ftp or scp to transfer the file
If your FreeBSD virtual machine has a web server that can serve the package you can repeat step #2 using the corresponding path.

6. Install package
If you copied the package using the web server method the package is already installed.
If you copied the package by other means then install package
#pkg add pkgcopiedpath

There is a procedure to install a GUI for e2guardian but I do not recommend it because it was made for a really older version of e2g.

There is another problem that has to be addressed. The mitm error page is made for apache as main web server.
pfsense uses gnix as main web server, so you have to configure e2g to use another web server or find a way to use gnix.
I use other web server so I can not help you with the gnix option.

It wont be easy to use the gnix. I think you will have to change the pfsense https web site to use other ssl port
as e2g will need the default ssl port to serve the error page. Before there where vhosts package available but now you have to do it withou the vhosts package.

marcelloc

Take a look on this thread for 2.3.x install instructions

https://forum.pfsense.org/index.php?topic=128116.0

jetberrocal

I looked into the script and see that it will install e2guardian from freebsd ports as is, with defaults.

If anyone wants to use mitm with e2g the defaults wont work.

I do not know if pfsense will let you run "make config" and then "make install" to activate the ssl support option.

I think it wont because "make" requires to have compilation packages in the system.

marcelloc

@jetberrocal:

I looked into the script and see that it will install e2guardian from freebsd ports as is, with defaults.

If anyone wants to use mitm with e2g the defaults wont work.

I do not know if pfsense will let you run "make config" and then "make install" to activate the ssl support option.

I think it wont because "make" requires to have compilation packages in the system.

If it's compiling fine on freebsd, I'll do soon a ssl compile to update the GUI to accept it and also test the upcoming v4

jetberrocal

In freebsd I run "make config" and then "make install" to activate the ssl support option. It worked successfully.

marcelloc

@jetberrocal:

In freebsd I run "make config" and then "make install" to activate the ssl support option. It worked successfully.

I've just create a 3.5.1 pkg on freebsd and installed on pfSense


e2guardian 3.5.1

Built with:  '--localstatedir=/var' '--with-logdir=/var/log' '--with-piddir=/var/run' '--enable-fancydm' '--disable-clamd' '--disable-commandline' '--disable-dnsauth' '--disable-email' '--disable-icap' '--disable-kavd' '--enable-ntlm' '--enable-trickledm' '--with-filedescriptors=4096' '--prefix=/usr/local' '--mandir=/usr/local/man' '--infodir=/usr/local/info/' '--build=amd64-portbld-freebsd10.2' 'build_alias=amd64-portbld-freebsd10.2' 'CXX=c++' 'CXXFLAGS=-O2 -pipe -I/usr/local/include -D__SSLMITM -D__SSLCERT -DLIBICONV_PLUG -fstack-protector -fno-strict-aliasing  -DLIBICONV_PLUG' 'LDFLAGS= -lssl -lcrypto -fstack-protector' 'LIBS=' 'CPPFLAGS=-I/usr/local/include -DLIBICONV_PLUG' 'CC=cc' 'CFLAGS=-O2 -pipe  -I/usr/local/include -D__SSLMITM -D__SSLCERT -DLIBICONV_PLUG -fstack-protector -fno-strict-aliasing' 'CPP=cpp' 'PKG_CONFIG=pkgconf'

and v4 beta too…

I'll see what will need to change on config files...

jetberrocal

Thank you marcelloc. I think that most of the guys waiting for e2g are expecting it with ssl support.

When do you expect for the package to be accepted in the freebsd ports?

marcelloc

@jetberrocal:

Thank you marcelloc. I think that most of the guys waiting for e2g are expecting it with ssl support.

When do you expect for the package to be accepted in the freebsd ports?

I did a first lookup on confi file changes. It will need some work to include all new features. But I could get ssl support working. ;D
I'll update the install process soon

On the todo list I'll include on help tab a way to see what package gui you are using and if there is an update.

If anybody wants to help the migration process, just look the TODO texts on e2gardian.conf.template and e2guardianfx.conf.template files on mu github repo.

marcelloc

Package install now includes 3.5.1 version with ssl support.

jetberrocal

@marcelloc:

@jetberrocal:

In freebsd I run "make config" and then "make install" to activate the ssl support option. It worked successfully.

I've just create a 3.5.1 pkg on freebsd and installed on pfSense


e2guardian 3.5.1

Built with:  '--localstatedir=/var' '--with-logdir=/var/log' '--with-piddir=/var/run' '--enable-fancydm' '--disable-clamd' '--disable-commandline' '--disable-dnsauth' '--disable-email' '--disable-icap' '--disable-kavd' '--enable-ntlm' '--enable-trickledm' '--with-filedescriptors=4096' '--prefix=/usr/local' '--mandir=/usr/local/man' '--infodir=/usr/local/info/' '--build=amd64-portbld-freebsd10.2' 'build_alias=amd64-portbld-freebsd10.2' 'CXX=c++' 'CXXFLAGS=-O2 -pipe -I/usr/local/include -D__SSLMITM -D__SSLCERT -DLIBICONV_PLUG -fstack-protector -fno-strict-aliasing  -DLIBICONV_PLUG' 'LDFLAGS= -lssl -lcrypto -fstack-protector' 'LIBS=' 'CPPFLAGS=-I/usr/local/include -DLIBICONV_PLUG' 'CC=cc' 'CFLAGS=-O2 -pipe  -I/usr/local/include -D__SSLMITM -D__SSLCERT -DLIBICONV_PLUG -fstack-protector -fno-strict-aliasing' 'CPP=cpp' 'PKG_CONFIG=pkgconf'

and v4 beta too…

I'll see what will need to change on config files...

Marcelloc.

Just received noticed there is a critical error with Google Chrome that was fixed on e2g 4.1

Please provide some partial package using this version as soon as posible, as previous versions are unusable due to the Chrome error.
It says to be backward compatible.

marcelloc

It's already updated. Just rerun the installation script.

https://github.com/marcelloc/Unofficial-pfSense-packages/commit/36678fe4cb3868065f5f84d90796c76fe515045c

jetberrocal

@marcelloc:

It's already updated. Just rerun the installation script.

https://github.com/marcelloc/Unofficial-pfSense-packages/commit/36678fe4cb3868065f5f84d90796c76fe515045c

Thank you for your excellent work.

bedmakaveli

Hello guys,
first of all, thanks for all the work done due to implement this features!! Expecially Marcello!

@pfSense2User:

I am trying to enable the clamav in the e2guardian program, but alas, I get an error that is shown on my monitor:
Aug 17 20:56:44 e2guardian[86361]: Unable to load plugin config /usr/local/etc/e2guardian/contentscanners/clamdscan.conf
I'm guessing this is still in a working progress? However, I'm glad that the squid3 comes with the clamav, but I like the e2guardian (formally Dansguardian) access denied error when it finds a virus on a site, like eicar's test antivirus.

I'll post back if I found a solution (temporarily speaking).

I have the same issue, I've tried to comment it on the conf file, but it's been recreated on every modify.
How can I fix this?

Thanks for any help!

marcelloc

@bedmakaveli:

I've tried to comment it on the conf file, but it's been recreated on every modify.
How can I fix this?

Select none on antivirus integration instead of auto.

belt9

Is this going to become an official pfSense package at any point in the foreseeable future?

marcelloc

I'll send a pull request for the official repo probably when v5 gets stable

bedmakaveli

Hello guys,
here I am again :) .
After setting all up, and get E2guardian working correctly, I would love to redirect to the courtesy page also for https pages.
I've read a lot of posts without finding something clear.
I'm using explicit proxy setting, so i don't need the MITSSL, or at least I think so.
There is a way to redirect the https pages to the courtesy page visualized on blocked http traffic or should i lose my hopes?

Thanks marcelloc for all the work, I'll repay the efforts with a lot of coffes :)