Stories
Slash Boxes
Comments

News for nerds, stuff that matters

Slashdot Log In

Log In

Create Account  |  Retrieve Password

SCO Chair's Anti-Porn Act Advances In Utah

Posted by kdawson on Thu Mar 15, 2007 08:51 AM
from the set-the-evil-bit dept.
iptables -A FORWARD writes "Gov. Jon Huntsman Jr. of Utah reportedly plans to sign a resolution urging Congress to enact the Internet Community Ports Act. The ICPA proposes that online content be divided by port, rather like TVs have channels with adult and family content, so that certain internet ports will be 'clean' — so-called Community Ports — and others will be 'dirty.' Thus, they hope to remove objectionable content from port 80 and require that it be moved elsewhere (port 666 was already taken by Doom, sorry), so that people could more easily block objectionable content, or have their ISPs do the blocking for them. This concept is being pushed by the CP80 group, which is chaired by Ralph Yarro, who also chairs the SCO Group. That probably explains why they didn't choose to adopt RFC 3514, instead."
+ -
story
This discussion has been archived. No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More
Loading... please wait.
  • This is about as enforceable as the .xxx TLD. No matter what you do, you're not going to be able segregate the pr0n from other content. Unless you're SCO, I guess, then maybe you could sue those who don't comply by claiming that your intellectual property is on port 80, therefore you own all of the content on port 80 -- millions of lines of HTML!
  • dotXXX (Score:4, Insightful)

    What makes this approach that much different from using the .XXX top-level? That's just as easily blocked, and easily passable (ssh or proxy)
    • Re:dotXXX (Score:5, Insightful)

      by SCHecklerX (229973) <slshdt@freefall.homeip.net> on Thursday March 15 2007, @09:21AM (#18360853) Homepage
      If they must have something (not that I agree), a .kids would make more sense. Then parents can configure their home proxy to only allow traffic to *that* domain. But, based on crap I see like religious shows on tv having a 'G' rating (WHAT? If anything requires parental guidance...), this would not work either. Maybe require a license to have and keep a .kids TLD or something.
  • "There is this assumption that you can't control it (the Internet)," Yarro said. "It's a toaster, we made it, we can fix it. ... We can solve the Internet pornography problem tomorrow if we decided to."

    Stupid legislators. It's not a fricking toaster, that's rediculous.

    It's a series of tubes.

    I thought we got that straight a few months ago!
  • by BGraves (790688) on Thursday March 15 2007, @09:06AM (#18360693)
    To all legislators:
            Please leave the internet alone. It works well. People smarter than you created it. It has revolutionized our world. Parents need to take care of their kids, not you. The more changes you make, the more likely you are to break something. Here's a deal. You don't need to get in the news to get my vote. Stay out of the news for a year, and I'll vote for you.
  • Another genius idea from people who know absolutely nothing about how computers or the internet functions. Ports are for protocols, not content. The "content" is just a paticular arrangement of data sent over that protcol.

    What these guys really want is to mandate that all IPv6 packets have a TOTC(Think of the children) bit. Defaulted to 1, for "unsafe content". They then pass legislation banning ISPs from handling anything with a TOTC bit of 1. The only way to get a TOTC bit of zero, without breaking the law, is to apply for an extremely expensive licence and audit, available to only the largest corporations.

    Entirely coincidentally, the Chinese government's UFTP(Unsafe for the People) bit will occupy exactly the same position in their altered version of the IPv6 protocol, ensuring that the new, saer net will be fully interoperable.

    Farfetched? Well, which is more likely? This or competant government that's for the people?
  • and In Absurdium (Score:5, Insightful)

    by boyfaceddog (788041) on Thursday March 15 2007, @09:52AM (#18361169) Journal
    1) Pass legislation to block evil pr0n from innocent kiddies by assigning it to a special port
    2) Make it acceptable for an ISP to block an entire port,
    3) Pass more legislation forcing some services onto certain ports (and allowing ownership of other ports (just like tv))
    4) Buy up ports and force ISPs to pay to use those.
    5) Both profit AND control of file sharing.

    STOP THIS LAW!!!
  • by fudgefactor7 (581449) on Thursday March 15 2007, @10:21AM (#18361509)
    "There is this assumption that you can't control it (the Internet)," Yarro said. "It's a toaster, we made it, we can fix it. ... We can solve the Internet pornography problem tomorrow if we decided to."

    What Internet Porn problem? [straightdope.com] Nevermind the silly thought of the 'Net being a toaster.
    • No, Only SCO would think that the state government of Utah controls the world.

      Anybody else would laugh - how the hell do they think that they can make this work, when most of the people in that industry AREN'T IN UTAH!
      • by Drantin (569921) * on Thursday March 15 2007, @09:24AM (#18360879)
        It was an April Fool's joke a few years back... look at the date on it...
      • by db32 (862117) on Thursday March 15 2007, @09:26AM (#18360897) Journal
        I honestly hope you don't think that is a real RFC. I really really hope that this is just a misunderstood attempt at sarcasm. Just in case it's not. Please check the date on that RFC, and then search through all RFCs for that same date...you might get the joke. Or you may just be very angry about the CHIMP protocol...
      • by Anonymous Coward on Thursday March 15 2007, @09:32AM (#18360975)
        Umm...what? Where the hell do "hackers" and "malicious packets" come into this?

        We're talking about content. And, to be honest, a voluntary system for identifying "adult material" would probably be adhered to. Because it's in the porn industry's best interest.

        The porn sites are in business to make money. Period. And they're well aware of negative image that they give the rest of the industry, and that there's a lot of heat on them. Frankly, it helps them a lot to be able to say "look, we provide technical means to allow parents to filter this out for their children." Now they can do business in peace, without the hue and cry of "Think of the Children! We must protect them from teh interwebs!"

        Is it possible to circumvent this system? Absolutely. Will some people fail to adhere to it? Without doubt. But most of the "legit" porn industry would probably be relieved to have a system that lets them say they're acting in good faith as responsible citizens.

        The problem here is the implementation, not the concept. Segregating content by internet port is just silly. And the underlying concept is somewhat disturbing--I think the notion here is like broadcast and basic TV, and FCC decency standards could be enforced on port 80. Frankly, that has a LOT of negative implications that have nothing to do with porn.

        Simpler to implement solutions that would achieve the same effect: Add a new TLD for porn (though IMO the proliferation of TLD's in also flawed, but that's a different rant), adding a specific meta-tag (just as we do today for robots), adding a new attribute to the tag to classify certain images as adult-only, etc. I'm sure there are better ideas than mine out there.

        At some point, people who are ACTUALLY concerned about children are going to stop trying to figure out how to somehow outlaw porn and work with the industry to put voluntary controls in place.
    • Re:Port 69 (Score:5, Informative)

      by PeterBrett (780946) on Thursday March 15 2007, @09:01AM (#18360641) Homepage

      Unfortunately port 69 is already assigned. From my /etc/services:

      tftp 69/tcp
      tftp 69/udp

      In any case, the concept is fundamentally flawed. Ports are designed to discriminate by protocol, not by service content. This is just another flawed implementation of RFC3514 [ietf.org].

      • More information... (Score:5, Informative)

        by PeterBrett (780946) on Thursday March 15 2007, @09:21AM (#18360847) Homepage

        More information on this subject, including a detailed discussion of why content segregation is dangerous, can be found in RFC3675 [ietf.org]. It suggests an actual workable solution: PICS tags.

        PICS Labels (Platform for Internet Content Selection) is a generalized system for providing "ratings" for Internet accessible material. The PICS documents [w3.org] should be consulted for details. In general, PICS assumes an arbitrarily large number of rating services and rating systems. Each service and system is identified by a URL.

        It would be quite reasonable to have multiple PICS services that, in the aggregate, provided 300 bits of label information or more. There could be a PICS service for every community of interest. This sort of technology is really the only reasonable way to make categorizations or labelings of material available in a diverse and dynamic world.

        While such PICS label services could be used to distribute government promulgated censorship categories, for example, it is not clear how this is any worse than government censorship via national firewalls.

        A PICS rating system is essentially a definition of one or more dimensions and the numeric range of the values that can be assigned in each dimension to a rated object. A service is a source of labels where a label includes actual ratings. Ratings are either specific or generic. A specific rating applies only to the material at a particular URL [RFC 2396 [ietf.org]] and does not cover anything referenced from it, even included image files. A generic rating applies to the specified URL and to all URLs for which the stated URL is a prefix.

        This seems like very much the "right" way of doing it. It:

        1. Doesn't break any existing systems,
        2. Is plenty flexible enough to be used for flagging pr0n as such, but also could be used by services like del.icio.us to suggest similar content to the current page,
        3. And gracefully degrades to support systems that are unaware of it.

        Also, unlike their proposed port breakage, it can easily be turned off if you don't care about it.

    • by jasenj1 (575309) on Thursday March 15 2007, @09:22AM (#18360863)
      How about:

      80085
      (I know it's not valid. It's a joke, son. Laugh.)
    • by Rob T Firefly (844560) on Thursday March 15 2007, @09:13AM (#18360759) Homepage Journal

      As a parent, I like the idea that I could install a port blocker at home and block the majority of porn content.
      Sure, it's a nice idea to think about, but it's also completely and totally impossible to implement or enforce. Suggesting we put all the adult content on this big unregulated international mishmash of an Internet on a specific port is pretty much like saying "we could stop all hunger in the world just by not letting anyone run out of food anymore, and we could stop all war by making sure nobody has a gun who is a war person." It just doesn't work that way.

      Sure, you could send your kid into Toys backwards-"R" Us alone without him finding porn (although if your kid is very young you should be going into the damn store with him,) but can you say the same of the Library of Congress? They have naughty books there. The Internet is much more an all-encompassing library than it is a kiddie-friendly toy shop, and it is nobody's responsibility but yours to monitor what your kid does with it.
    • by saider (177166) on Thursday March 15 2007, @09:15AM (#18360795)
      This is not a technology problem. It is a problem of figuring out who gets to set the porn bit. Since the internet is international no one jurisdiction can assert authority. For your meatspace analogy, it would be like you lighting up a joint, and then telling the LA police to piss off because it is legal in Amsterdam.
        • I was going to make a hardcore double penetration input-in-the-output-port joke, but then I started thinking about how many networking geeks would jump all over the joke based on the fact that double penetrating the pron port would cause a tcp/ip collision, and therefore no penetration would occur, and I gave it up as a lost cause.