Printable View
Came across an add-on that allows the firefox browser to access facebook sites using HTTPS. Really concern about this and wondering besides esoft, is there any other way to overcome this?
Was thinking of blocking the IP addresses, but then how many IPs do Facebook sits on?
nslookup facebook.com
you will get alot, also dependant on what location your in, i once blocked all of the ones that came up in CR nslookup, but of course it just found another IP outside of the ones i blocked.
i really hate that sites are doing their best to not be blocked and find way around it, i guess UTM's are going to have to find ways to stop HTTPS traffic sometime.
There's actually an add-on now that forces https for all sites that support it. That could cause a big headache for web filtering.
Its more a human resources that tech problem I think.
IT born with this. Today is facebook or P2P, yesterday porn, and tomorrow who know.
Is a race that we are always one step behind.
I have assumed that it is impossible to detect and block all. But look at trends and patterns suspects.
Clear rules (read about aceptable uses policy), punishment, and support from the head of the company.
Mathiau - Tot of that at first. But then it's HTTPS. If were to place the FB IPs under the blocked sites, it will still pass thru.Quote:
Originally Posted by Mathiau
No, if you use the firewall to block access to an IP address, or the eSoft filter to prevent access to a specific IP address or range... it will stop the traffic.
The trouble is in SSL, even the URL is encrypted. All the Untangle can really see is the destination IP address, and the source IP address. The rest of the packet is mangled.
Yup. You're right. If only that's possible. The factor affecting my situation is that some users are allowed to FB (for work related). My concerns are those not allowed and they found this method.Quote:
Originally Posted by sky-knight
have to do a firewall rule then blocking FB, then a rule ABOVE that one that allows it for specific internal IP's.