Dont Worry Government, I Got This Porn Filter Sorted

Post by bigiain » Mon, Jul 29, 2013, 12:08 AM UTC

rmc wrote: post #14

sehrope wrote: post #6

> Any request that is denied by OpenDNS is then allowed by our DNS server, and any request allowed by OpenDNS is blocked by us. The most interesting part of this to me is using multiple DNS providers to determine which category the site is in. It's both simple and effective. If they actually go ahead with this plan in the UK and it's implemented similarly (eg. via DNS rather than IP blocking), somebody should make a…

They can't and don't do it with just a DNS, it'll have to be DNS + HTTP URL. Otherwise porn hosted on one large shared hosting would block everything. (e.g. imagine if the Amazon EC2 DNS got blocked). The current UK ISP filter (the one that already filtered Wikipedia), used DNS & HTTP. IP addresses that needed filtering were redirected to their HTTP server by sending back their IP address, and then a HTTP proxy was u…

Post by nickik » Mon, Jul 29, 2013, 3:39 AM UTC

allinzen wrote: post #33

Brilliant! Now only if there was a cat filter that only showed cats and cat related material.

Post by cmircea » Mon, Jul 29, 2013, 7:26 AM UTC

mpyne wrote: post #40

cmircea wrote: post #39

Earlier quoted context omitted.

What if the IP is dynamic? Say an Azure Cloud Service.

I think the problem is that you'd need a different X.509 certificate for TLS, for each and every single IP.