Squid 3.3.4 package for pfsense with ssl filtering

serialdie

Has anyone tried to use the "Time" setting to change squidguard filtering on this version of squid?

I don't know if this is a squid or a squidguard error, but the filters NEVER switch from On-Time to Off-Time and vice-versa…. ie, the "recalc trigger time" event never happens.

This has been a bug for YEARS, but I cannot seem to get any of the code developers interested in looking at the problem. They all point to a client caching problem, but that is definitely not the case. Squidguard log shows the redirect every time.

:(
Thanks for listening.

See:
https://forum.pfsense.org/index.php?topic=72251
https://forum.pfsense.org/index.php?topic=59671
https://forum.pfsense.org/index.php/topic,43352.0.html (nearly 7000 views!)

I feel your pain.
My work around this was to create a cronjob to HUP squid each off time.

usabug

I have the same issue . I cannot find a way to allow skype to work .
I use trasparent proxy for 80/443 with mitm. if someone knows a way hot to get it work please share it with us !!!

marcelloc

@erwintwr:

some entries from the squid log is generated below :

Create a host alias on pfsense and add


api.skype.com
conn.skype.com
ui.skype.com

Then put this alias on squid "Bypass proxy for these destination IPs" transparent option
Field description says
Do not proxy traffic going to these destination IPs, CIDR nets, hostnames, or aliases, but let it pass directly through the firewall. Separate by semi-colons (;). [Applies only to transparent mode]

If you are not using transparent proxy, a custom acl to keep .skype.com out of ssl interception may work.
http://www.squid-cache.org/Doc/config/ssl_bump/

postduif

I've got Squid with transparent SSL working, but sadly not for sites like gmail.com (mail.google.com works). A HSTS failure prevents chrome for opening the site. Is there any bypass for HSTS?

periko

I had setup ssl-bump and could navigate to different sites, gmail, google, facebook, paypal and even more, all of them use https.

The trick for me was to give my ca to each browser, on iexplore import the ca to the root, firefox was more detail because he ask u what rights u want to apply to the ca.

Just 1 failure with my bank site which I still cannot access with ssl-bump enable, but the browser doesn't give to much details of the issue.

The 2nd issue I found was with ebay, went I wanted to pay I receive this error:

The following error was encountered while trying to retrieve the URL: ://checkout.payments.ebay.com:443

Failed to establish a secure connection to site-ip

The system returned:

(92) Protocol error (TLS code: X509_V_ERR_UNABLE_TO_GET_ISSUER_CERT_LOCALLY)
SSL Certficate error: certificate issuer (CA) not known: /C=US/O=VeriSign, Inc./OU=VeriSign Trust Network/OU=Terms of use at https://www.verisign.com/rpa 10/CN=VeriSign Class 3 Secure Server CA - G3

This proxy and the remote host failed to negotiate a mutually acceptable security settings for handling your request. It is possible that the remote host does not support secure connections, or the proxy is not satisfied with the host security credentials.

What I did was to clear certs folders, empty index.txt, size folder value to 0, latter remove my ca from the browsers, create a new one and start over.

I could pay on ebay, the only issue I have is with my bank now, I will try to add the option that skip some sites from ssl-bump.

I still nervous if I can send this to production.

marcelloc

@periko:

I still nervous if I can send this to production.

with ssl interception you will always need a lot of tests.

I'm having some issues with some sites too, the workaround is to do not intercept sites I know or trust.

I'm still waiting squid 3.4 in freebsd ports. Since it's there, I'll update squid3-dev.

gzartman

I've been working to get ssl bumping working on windows 7 & 8 clients, but I continue to get SSL Certificate errors.

I'm running latest PFsense 2.1, and installed squid3-dev from the repo.

I created a CA in the certificate manager, then clicked on SSL Man in the middle filter in the Proxy Server panel. I'm running squid as a transparent proxy, so input port 443 in the port number field. I then select my CA create in the CA field.

I'm not sure if I need to select any of the options in Remote Cert checks and Certificate adapt fields, so I'm just accepting defaults (i.e., selecting none).

I then download the CA on my windows machines and install them as Trusted Root CAs using the certmgr.msc windows application. When I browse to google.com in both firefox and chrome, I get certificate errors.

Am I missing a setting in the SSL man in the middle panel or some other setting?

Thanks,

greg

periko

Don't know if this helps, but if u run ccleaner to clear cache in all your browsers before testing, does this helps?

exograpix

Squid ssl filtering not working, it used to work 3 days back, but now certificate error are popping all over. please suggest.

marcelloc

You have to import pfsense-ca crt on firefox too, internet explorer and chrome uses certmgr.msc imported cert.

I'm testing it a lot without any cert issues on any sites.

exograpix

Hi,

I have loaded ca certificate in trusted root certificate and webconfigurator certificate in personal (through certmgr.msc). but still shows certificate error in internet explorer. please suggest what to do.

exograpix

In spite of all my effort still certificate error as soon as I enable ssl filtering , help guys.

marcelloc

@exograpix:

I have loaded ca certificate in trusted root certificate and webconfigurator certificate in personal (through certmgr.msc). but still shows certificate error in internet explorer. please suggest what to do.

the only place you need is trusted root certificate on ie and firefox.

Sure it works.

screenshot the certificate you get when firefox rejects.

postduif

@marcelloc:

@exograpix:

I have loaded ca certificate in trusted root certificate and webconfigurator certificate in personal (through certmgr.msc). but still shows certificate error in internet explorer. please suggest what to do.

the only place you need is trusted root certificate on ie and firefox.

Sure it works.

screenshot the certificate you get when firefox rejects.

It doesn't work any longer since I've updated to pfSense 2.1.1
It worked on 2.1

exograpix

Thats my problem too , I have tried all combination but doesn't work, it used to work earlier quite smoothly, but somehow it stopped working now.

I request to sort this issue out asap to help the community and existing installs.

bellera

@postduif:

It doesn't work any longer since I've updated to pfSense 2.1.1
It worked on 2.1

Need to see which system things changed with the upgrade.

Verify the "orphan" libraries for squid3-dev and what about OpenSSL?

OpenSSL does not like country codes longer than two letters, so remove entries that are not actually country codes

https://doc.pfsense.org/index.php/2.1.1_New_Features_and_Changes

exograpix

I have used the standard process as pfsense 2.1 (now even in previous version ssl certificate error is popping)

I installed pfsense.

Created the internal CA.

Created the server certificate (tried client too)

Import CA certificate through certmgr.msc in trusted root

Import other certificate in personal

copied missing files for squid.

Installed squid-dev from packages.

Configured squid as before with ssl filter and certificate and boom even microsoft default certificate error.

postduif

@bellera:

@postduif:

It doesn't work any longer since I've updated to pfSense 2.1.1
It worked on 2.1

Need to see which system things changed with the upgrade.

Verify the "orphan" libraries for squid3-dev and what about OpenSSL?

OpenSSL does not like country codes longer than two letters, so remove entries that are not actually country codes

https://doc.pfsense.org/index.php/2.1.1_New_Features_and_Changes

Checked, and the orphan libraries are on the system. Countrycode is 2 letters.
Squid http filtering works fine, only the https part results in certificate errors.

exograpix

https is the problem and it is major concern now.

bellera

pfSense 2.1 (not upgraded to 2.1.1)
squid3-dev upgraded from 3.3.10 pkg 2.2.1 to 3.3.10 pkg 2.2.2

Bug for interception

Last lines of squid.conf generated by 2.2.1

# Custom options

always_direct allow all
ssl_bump server-first all
# Setup allowed acls
# Allow local network(s) on interface(s)
http_access allow localnet
# Default block all to be sure
http_access deny allsrc

Last lines of squid.conf generated by 2.2.2

# Custom options before auth

# Setup allowed acls
# Allow local network(s) on interface(s)
http_access allow localnet
# Default block all to be sure
http_access deny allsrc

Workaround until next version

Put at Custom ACLS (Before_Auth) box the lines

always_direct allow all
ssl_bump server-first all

Custom ACLS (After_Auth)

In addition to this, the box Custom ACLS (After_Auth) does nothing.

Rotate Cron duplicated

The upgrade also duplicates the rotate cron. You can see it if you have Cron package installed

0  	0  	*  	*  	*  	root  	/bin/rm /var/squid/cache/swap.state; /usr/pbi/squid-i386/sbin/squid -k rotate -f /usr/pbi/squid-i386/etc/squid/squid.conf  	
0  	0  	*  	*  	*  	root  	/usr/pbi/squid-i386/sbin/squid -k rotate -f /usr/pbi/squid-i386/etc/squid/squid.conf

Delete the old cron containing rm swap.state and look up the new option Proxy server: Cache management: Clear cache on log rotate

Discussion about the new option, https://forum.pfsense.org/index.php?topic=74453.msg407287#msg407287

More about squid duplicated cron, https://forum.pfsense.org/index.php?topic=74633.0