Skip to main content

Internet Zoning Initiative, and why it's stupid

Usually I'm not very vocal about 'policy' ideas.  Things that may become law in other words..  But I read this article as a recommendation from Marc Sachs.  We were sitting in the ISC chat room last night, he asked us if we had read it, and I said no.  So I grabbed the pdf and here I am blogging about it.

So essentially what the Internet Zoning Initiative is, is the ability (trying to become a requirement) for lawmakers to tell web providers to essentially make different "channels" out of the web.

For instance, if you had a website that had normal content and adult content, it would require you to run a "Child-free" website on port 80, then, using virtual hosting, run your adult website on port 69.  (Or whatever.)  Here's an example they give in their pdf:

Now, this, to me, is like asking a kid to click on, "Are you above the age of 18?  Yes, or No".  If a teenager (or adult for that matter) wants to go and look at whatever they want to look at, what are they going to click? 

Yeah, I can just imagine a kid now, sitting behind his desk at home, "Oh wait, I'm not 18, let me click No."  Come on people.

All you are doing is saying that basically the kid has to either click on the link on your port 80 website to go to your port 69 website.  OOhh!!  What protection!  Even that, hey, I can just add http://urlgoeshere:69 to my browser address bar, and thusly, I am there man!

I think this whole idea is founded well.  Okay, so you want to protect kids on the internet, fine.  I have no problem with that idea.  But the idea that you have here is a bit off base.  I've heard that OS X's parental controls are quite good.  However, never having tested them, I can't endorse them either yet.  But the idea of putting porn on a totally different port isn't going to solve a THING.

The only idea that I have ever seen that was at least descent was the invention of the ".xxx" domain for 'adult' content.  That's at least blockable and instantly distinguishable.  

Besides, let's look at the corporate implications for this.  Inline proxies would have to start listening on, essentially all ports.  IDS/IPS's would have to normalize http over any port, there would be all kinds of holes poked in the firewalls..  It's just not feasible.  Sorry, try again.



 Subscribe in a reader

Comments

/ip said…
Dude! It's like the TV shows that say..."This contains adult content...blah blah blah...". It means keep watching!
/ip said…
Wow...to much to drink...nmap -p 69...
/ip said…
Dude! It's like the TV shows that say..."This contains adult content...blah blah blah...". It means keep watching!
/ip said…
Wow...to much to drink...nmap -p 69...
woodcat said…
Hi.
Very interesting for me, just say the normak things.
Good Speach...

Can I transate and upload with the proper rights, off course?
Joel Esler said…
That's fine as long as my license is adhered to:
http://creativecommons.org/licenses/by-sa/3.0/us/
woodcat said…
Hi.Very interesting for me, just say the normak things.Good Speach...Can I transate and upload with the proper rights, off course?
Joel Esler said…
That's fine as long as my license is adhered to:http://creativecommons.org/licenses/by-sa/3.0/us/

Popular posts from this blog

Offset, Depth, Distance, and Within

Without going off the deep-end here and discussing every single Snort rule keyword, I just wanted to touch on a few modifiers that people sometimes misunderstand.  They aren't difficult, and hopefully after this explanation and a few examples, I can clear some of the air around these five modifiers.

The five modifiers that I am talking about are
OffsetDepthDistanceWithinnocaseThese five modifiers are not keywords of themselves, but rather they apply as modifiers to another keyword.  That keyword is "content". The content keyword is one of the easiest pieces of the Snort rules language as all it does is look for a particular string.  So for instance if I wanted to look for the word "joel" within a packet.  A simple:
content:"joel";Would allow me to do that.  The interesting part comes into play when you want to specify where inside of a particular packet you want the string "joel" to be looked for.  If you are running just a plain content ma…

Writing Snort Rules Correctly

Let me start off by saying I'm not bashing the writer of this article, and I'm trying not to be super critical.  I don't want to discourage this person from writing articles about Snort rules.  It's great when people in the Snort community step up and explain some simple things out there.  There are mistakes, it comes with the territory.  If you choose to be one of the people that tries to write Snort rules, you also choose to be someone who wants to learn how to do it better.  That's why I write this blog post, not to bash the writer, but to teach.

I noticed this post today over at the "Tao of Signature Writing" blog, and to be honest I glanced over most of it figuring it was a rehash of things I've already read or things that have already been written from countless people about "Here's how you write Snort rules!".  I scrolled down quickly skimming, not reading at all really, and noticed this part:
Now, let us look at the second questio…

Safari 5.1.4 now available

Safari 5.1.4 now available, fixes issues and improves performance | TUAW - The Unofficial Apple Weblog:


Improve JavaScript performanceImprove responsiveness when typing into the search field after changing network configurations or with an intermittent network connectionAddress an issue that could cause webpages to flash white when switching between Safari windowsAddress issues that prevented printing U.S. Postal Service shipping labels and embedded PDFsPreserve links in PDFs saved from webpagesFix an issue that could make Flash content appear incomplete after using gesture zoomingFix an issue that could cause the screen to dim while watching HTML5 videoImprove stability, compatibility and startup time when using extensionsAllow cookies set during regular browsing to be available after using Private BrowsingFix an issue that could cause some data to be left behind after pressing the "Remove All Website Data" button