DNSBL Certificate errors
-
I followed this guide and dropbox is refused to connect.
DNSBL
May 28 14:34:43 Unknown Unknown www.google-analytics.com
Not available for HTTPS alertsMay 28 14:19:03 Unknown Unknown www.dropbox.com
Not available for HTTPS alertsboth show the domains are in the whitelist.
If and Source and Unknown and list shows no match.
-
Can you post a screenshot of the Whitelist and the Alerts Tab showing these blocked domains.
-
Currently the domains are whitelisted in the custom domain whitelist. Is this correct or should they go in the TLD whitelist
-
Currently the domains are whitelisted in the custom domain whitelist. Is this correct or should they go in the TLD whitelist
The Custom Domain Whitelist is used to "whitelist" domains…
The TLD Whitelist is only used in combination with TLD Blacklist… An example of that would be where you want to block all "ru" domains with TLD Blacklist, but you want to allow certain ru domains to get thru.
-
What is the option to not serve up a https image to avoid certificate errors in 2.1.1_8?
-
[ DNSBL FAIL ] [ Skipping : SuspiciousDomains ]
What feed URL are you using? There are three options available:
https://isc.sans.edu/feeds/suspiciousdomains_High.txt
https://isc.sans.edu/feeds/suspiciousdomains_Medium.txt
https://isc.sans.edu/feeds/suspiciousdomains_Low.txtOtherwise check that you didn't copy/paste the new patched line incorrectly…
-
After 2 weeks, I started getting certificate errors again. Strangely, pfblockerng.inc reverted to the original (dnsbl_vip). I replaced it and it works again.
If you make manual changes to the pfblockerng.inc file, those will be lost on a pkg installation. So you most likely installed v2.1.1_8 which reset the file back to default… The next release should have this fix built-in...
BBcan,
Just installed the next release and certificate error has returned. :( -
After 2 weeks, I started getting certificate errors again. Strangely, pfblockerng.inc reverted to the original (dnsbl_vip). I replaced it and it works again.
If you make manual changes to the pfblockerng.inc file, those will be lost on a pkg installation. So you most likely installed v2.1.1_8 which reset the file back to default… The next release should have this fix built-in...
BBcan,
Just installed the next release and certificate error has returned. :(Sorry to get your hopes up… but the last release was just a small patch... Not quite finished with it yet...
-
The firewall rule worked! I changed my DNSBL SSL port to 8082 though since I have a Unifi controller running on my pfsense box on 8443.
-
Thanks for the links… It's not something that I would want for the package... MITM anything is bad in my books :)
I am working on improving this issue… So stay tuned...You can decide what to include in your package. But pixelserv-tls is not MITM blah.
-
Creating custom certs for domains you don't own is a MITM method.
Not that it would work for google.com as they use HSTS preloading and public-key pinning. Browser makers bake information about the certificate chain for some sites into the package/installation. The browser knows about the certs it should be expecting for those sites before a request is even made and will warn the user if the certificate has been tampered with.
First time I hear such a definition of MITM. Maybe you have a point. Perhaps blocking ad by poisoning DNS record shall be in this category too.
Your understanding of HSTS and what's built in chrome/firefox doesn't seem right to me.
-
Just my 2 cents not sure of implications but since upgrading to IOS 11.0.3(including the 3 IOS updates in the last 2-3 weeks), I used to get a pop-up's on my iPhone safari…now I get a "safari cannot open...could not establish a secure connection...".
In firefox on Linux I got redirected to a certificate error...went thru and made an exception...now I get the 1x1 pixel page.
I'll take a cert error or 1x1 pixel page...just no spying!!!
I love you BBCAN!
-
I've tried
Action: Reject
Interface: LAN
Address Family: IPV4
Protocol: TCP
Source: any
Destination: Single host or alias 127.0.0.1 or 10.10.10.1
Destination port range: custom 8443 (in both custom fields)DNSBL configuration
DNSBL Virtual IP 127.0.0.1 or 10.10.10.1It does prevent the certificate errors but doesn't block the ads on the yahoo.com home page on ipad or macbook pro
If I edit the code in the on line 3636 in /usr/local/pkg/pfblockerng/pfblockerng.inc to
$domain_data .= "local-data: \"" . $line . " 60 IN A 0.0.0.0\"\n";No certificate error but doesn't block the ads on yahoo.com home page on ipad or mackbook pro
I did reload the DNSBL.
My version of pfBlockerNG is 2.1.2Not sure what I'm doing incorrectly.
-
Hi folks - I was wondering if others that have upgraded to pfsense 2.4.1 are having the certificate errors again? Previously in 2.3.4 the solution described above was working fine with the lan rule blocking any traffic to the dnsbl vip. Post upgrade to 2.4.1 I'm getting certificate errors again from my AV solution. This began happening immediately after upgrade of pfsense to 2.4.1.
Anyone else having this trouble?
-
Hi folks - I was wondering if others that have upgraded to pfsense 2.4.1 are having the certificate errors again? Previously in 2.3.4 the solution described above was working fine with the lan rule blocking any traffic to the dnsbl vip. Post upgrade to 2.4.1 I'm getting certificate errors again from my AV solution. This began happening immediately after upgrade of pfsense to 2.4.1.
Anyone else having this trouble?
I'm on 2.4.1 with the latest PFBlocker installed, I haven't gotten the certificate errors at all. When I was on 2.3.4 I had to edit the file or I would get certificate errors.
-
Can you share your dnsbl configuration and any lan / float rules you may have on this? I'm hoping it's some minor configuration change i need to make instead of a full re-install.
-
No more certificate errors on the 2.4.1 and latest version of pfblocker. This was a fresh installation.
-
anyone figured out (with pfblockerng 2.1.2-1) why blocking of 127.0.0.1 or 10.10.10.1 port 8443 is not working anymore to stop the certificate error messages with the current version of pfsesne (2.4.1)?
Is there a solution that does not include the editing of the inc-file with 0.0.0.0?
-
I still have the issue. Currently i have dnsbl turned off and using pihole until it get's figured out.
-
anyone figured out (with pfblockerng 2.1.2-1) why blocking of 127.0.0.1 or 10.10.10.1 port 8443 is not working anymore to stop the certificate error messages with the current version of pfsesne (2.4.1)?
Is there a solution that does not include the editing of the inc-file with 0.0.0.0?
The only thing that changed was a recent commit to add the "Filter rule association" in the NAT rules. It was not previously defined, and since was changed to "pass"…
https://github.com/pfsense/FreeBSD-ports/commit/b4afa470b6599acfd48f902322452ee426995d76#diff-2fbe23c4e674f981e4a4003fb2794b27
Next release will have functionality to force "0.0.0.0" for a DNSBL group to avoid this issue....
