Guide to filtering web content (http and https) with pfsense 2.3
-
Can't get HTTPS scanning to work. See https sites passing through squid but clamd won't scan the files. Works fine on HTTP and it catches the virus files. Using proxy setting in browser since wpad isn't giving the results I am expecting.
Same issue here now.
I enabled the 80-443 block rule, unchecked the 'Transparent" option in Squid and I can only get access if I manually enter the wpad.dat location into my local computer(s) settings. Auto discovery does not work. I'm on all Apple computers/devices here btw. Same issue with ClamAV, it scans http but not https as poster above.
-
Auto config works for me. What I meant in the original post was that the WPAD direction info I was writing was not proper hence was using straight proxy settings for the time being. Will be experimenting with the WPAD file at a later time.
I seriously doubt HTTPS scanning (not filtering) with clamd is working. I have followed the configuration directions to the T and yet the only thing which does not work is https clamd scans for viruses. I believe its a Squid issue.
-
Post a link to the https fake virus test file that you are testing and I will see if it works for me.
-
http://www.eicar.org/85-0-Download.html
There is one group for http, and one group for https.
-
There are 4 https links
https://secure.eicar.org/eicar.com
https://secure.eicar.org/eicar.com.txt
https://secure.eicar.org/eicar_com.zip
https://secure.eicar.org/eicarcom2.zip -
Would you know how to get the below google safesearch info in pfSense BIND DNS?
server: include: /var/unbound/forecegoogle.conf
-
Ok done some research squidclamav only supports http not https because it is encrypted.
would you know how to get the below google safesearch info in pfSense BIND DNS?
Not sure you will need to ask that in the proxy forum.
-
Ok done some research squidclamav only supports http not https because it is encrypted.
I just did a test. Squidclamav will scan https traffic when using Squids MITM option..
-
Ok done some research squidclamav only supports http not https because it is encrypted.
I just did a test. Squidclamav will scan https traffic when using Squids MITM option..
And that would need certificates have to be installed on the clients..
-
Ok done some research squidclamav only supports http not https because it is encrypted.
I just did a test. Squidclamav will scan https traffic when using Squids MITM option..
And that would need certificates have to be installed on the clients..
Correct.
-
To help stop virus or spywhere we can enable squidguard block list blk_BL_spyware,
-
What is the point of all the safesearch nonsense and redirecting users to only use your dns.. You do understand when a proxy is being used, the proxy does the query not the client..
-
While setting up wpad we'r supposed ot enter the following into /usr/local/www/wpad.da:
function FindProxyForURL(url, host)
{
if (isPlainHostName(host) ||
shExpMatch(host, "*.local") ||
isInNet(dnsResolve(host), "192.168.1.0", "255.255.255.0"))
return "DIRECT";return "PROXY 192.168.1.1:3128";
}I've actually changed my pfsense server ip to 192.168.0.1 - do I need to edit both ip addresses listed above?
-
What is the point of all the safesearch nonsense and redirecting users to only use your dns.. You do understand when a proxy is being used, the proxy does the query not the client..
I think the point of the safe search is to stop, say your young kids, from Googling porn images. I'm not sure about the dns redirecting.
-
What is the point of all the safesearch nonsense and redirecting users to only use your dns.. You do understand when a proxy is being used, the proxy does the query not the client..
I think the point of the safe search is to stop, say your young kids, from Googling porn images. I'm not sure about the dns redirecting.
1. What is the point of forcing search engines from using safe search?
Answer: To aid in the filtering of adult content, this is most importantly for google images as squidguard does not block them, if you do not want to filter web content then this guide is not designed for you.2. What is the point of redirecting users to use THEIR pfsense router as the DNS server.
Answer: There are many advantages not all relating to web filtering however tries and stops the user from bypassing the dns redirect rule.While setting up wpad we'r supposed ot enter the following into /usr/local/www/wpad.da:
function FindProxyForURL(url, host)
{
if (isPlainHostName(host) ||
shExpMatch(host, "*.local") ||
isInNet(dnsResolve(host), "192.168.1.0", "255.255.255.0"))
return "DIRECT";return "PROXY 192.168.1.1:3128";
}I've actually changed my pfsense server ip to 192.168.0.1 - do I need to edit both ip addresses listed above?
Yes, set it to 192.168.0.0
-
I'm constantly getting these entries in the Squid Real Time log:
01.07.2016 06:06:34 192.168.1.5 TCP_DENIED/403 127.0.0.1:59488 - - 01.07.2016 06:06:34 192.168.1.5 TCP_DENIED/403 127.0.0.1:55735 - - 01.07.2016 06:06:34 192.168.1.5 TCP_DENIED/403 127.0.0.1:49806 - - 01.07.2016 06:06:34 192.168.1.5 TCP_DENIED/403 127.0.0.1:46365 - - 01.07.2016 06:06:34 192.168.1.5 TCP_DENIED/403 127.0.0.1:38156 - - 01.07.2016 06:06:34 192.168.1.5 TCP_DENIED/403 127.0.0.1:25012 - - 01.07.2016 06:06:34 192.168.1.5 TCP_DENIED/403 127.0.0.1:24866 - - 01.07.2016 06:06:33 192.168.1.5 TCP_DENIED/403 127.0.0.1:14826 - - 01.07.2016 06:06:33 192.168.1.5 TCP_DENIED/403 127.0.0.1:10196 - - 01.07.2016 06:06:33 192.168.1.5 TCP_DENIED/403 127.0.0.1:6263 - -
192.168.1.5 is my local machine. Is this normal?
Update: Resolved this in another thread..
-
To stop users from bypassing your proxy setup a new firewall lan rule and block port 80 and 443
Just to clarify - this is to prevent users from bypassing the proxy altogether, rather than just bypassing the autoproxy/wpad stuff?
-
The Squid Guard settings aren't working for me. I download the blacklist and then go to Common ACL (I've already completed the target categories step on a previous run through), but the "Target Rules" only contains "^whitelist all" and there are only [whitelist] and Default access [all] options there.
On another point, I don't want to have to set up auto proxy for every device connecting to my network - would it work if I use transparent proxy and then explicitly set the https_proxy on the couple of machines I really need locked down?
-
To stop users from bypassing your proxy setup a new firewall lan rule and block port 80 and 443
Just to clarify - this is to prevent users from bypassing the proxy altogether, rather than just bypassing the autoproxy/wpad stuff?
If port 80 and 443 are lefted open then the user can simply untic the auto configure proxy (on their PC, Mac, phone etc) and set the setting to go direct. This will not call for the wpad and the user will go direct and not use the proxy.
The Squid Guard settings aren't working for me. I download the blacklist and then go to Common ACL (I've already completed the target categories step on a previous run through), but the "Target Rules" only contains "^whitelist all" and there are only [whitelist] and Default access [all] options there.
On another point, I don't want to have to set up auto proxy for every device connecting to my network - would it work if I use transparent proxy and then explicitly set the https_proxy on the couple of machines I really need locked down?
1.With squidguard set default access to allow then set the categories you want to deny. Save and then go to squidguard General settings and hit apply. Please read the tip under this section it is very important.
Read this https://doc.pfsense.org/index.php/SquidGuard_package2. Transperrent proxy does not use a wpad, if you want to use transperrent proxy for http then you need SSL Man In the Middle Filtering for https which must have a certificate installed on evey device.
So you can either set auto configure proxy on all devices or install a certificate on all devices.
You cannot use a transperrent proxy and a wpad at the same time. If you did get a transperrent proxy with SSL mitm working then there is no need for manual proxy mode.
-
1.With squidguard set default access to allow then set the categories you want to deny. Save and then go to squidguard General settings and hit apply. Please read the tip under this section it is very important.
Read this https://doc.pfsense.org/index.php/SquidGuard_packageThat was the problem - there were no other categories than whitelist and default access. I managed to get the others by enabling "Blackilist" under the general settings of Squid Guard. Forgive me if I just missed it, but I couldn't see that step in the guide.