ICANNWatch
 
  Inside ICANNWatch  
Submit Story
Home
Lost Password
Preferences
Site Messages
Top 10 Lists
Latest Comments
Search by topic

Our Mission
ICANN for Beginners
About Us
How To Use This Site
ICANNWatch FAQ
Slash Tech Info
Link to Us
Write to Us

  Useful ICANN sites  
  • ICANN itself
  • Bret Fausett's ICANN Blog
  • Internet Governance Project
  • UN Working Group on Internet Governance
  • Karl Auerbach web site
  • Müller-Maguhn home
  • UDRPinfo.com;
  • UDRPlaw.net;
  • CircleID;
  • LatinoamerICANN Project
  • ICB Tollfree News

  •   At Large Membership and Civil Society Participation in ICANN  
  • icannatlarge.com;
  • Noncommercial Users Constituency of ICANN
  • NAIS Project
  • ICANN At Large Study Committee Final Report
  • ICANN (non)Members page
  • ICANN Membership Election site

  • ICANN-Related Reading
    Browse ICANNWatch by Subject

    Ted Byfied
    - ICANN: Defending Our Precious Bodily Fluids
    - Ushering in Banality
    - ICANN! No U CANN't!
    - roving_reporter
    - DNS: A Short History and a Short Future

    David Farber
    - Overcoming ICANN (PFIR statement)

    A. Michael Froomkin
    - When We Say US™, We Mean It!
    - ICANN 2.0: Meet The New Boss
    - Habermas@ discourse.net: Toward a Critical Theory of Cyberspace
    - ICANN and Anti-Trust (with Mark Lemley)
    - Wrong Turn in Cyberspace: Using ICANN to Route Around the APA & the Constitution (html)
    - Form and Substance in Cyberspace
    - ICANN's "Uniform Dispute Resolution Policy"-- Causes and (Partial) Cures

    Milton Mueller
    - Ruling the Root
    - Success by Default: A New Profile of Domain Name Trademark Disputes under ICANN's UDRP
    - Dancing the Quango: ICANN as International Regulatory Regime
    - Goverments and Country Names: ICANN's Transformation into an Intergovernmental Regime
    - Competing DNS Roots: Creative Destruction or Just Plain Destruction?
    - Rough Justice: A Statistical Assessment of the UDRP
    - ICANN and Internet Governance

    David Post
    - Governing Cyberspace, or Where is James Madison When We Need Him?
    - The 'Unsettled Paradox': The Internet, the State, and the Consent of the Governed

    Jonathan Weinberg
    - Sitefinder and Internet Governance
    - ICANN, Internet Stability, and New Top Level Domains
    - Geeks and Greeks
    - ICANN and the Problem of Legitimacy

    Highlights of the ICANNWatch Archive
    (June 1999 - March 2001)


     
    ICANN Staff and Structure ICANN Network Bugs
    posted by michael on Wednesday March 27 2002, @08:11AM

    Anonymous writes "A couple of network glitches showed up on ICANN's network, plus some interesting content on their web servers. The bugs are patched, but their demonstrated security skills make me queasy.

    In one case, a network switch controlling LANs with ominous names like "vlan-001-L-ROOT-01" (uh...as in "L Root Server"?) was publicly accessible and vulnerable to an old Cisco bug that let anyone with a web browser reconfigure it.

    In another instance, the source code and operational details of the system for WIPO, CPR, etc., to report UDRP cases and proceedings was on public web server."




    This included pointers to the publicly-accesible web sites used to modify the data, and passwords for the email-based system of doing the same. (Check out UDRP case WIPO D2002-9001 and look closely at the disputed domain name.) [Editor's note: you can do this by going to the UDRP search page and entering Start = 5440 End = 5600 as your search range...]

    While those security-related items were quickly patched when reported, there are still plenty of easter eggs at ICANN. There's probably a good reason why there's a copy of the enetRegistry web site on ICANN owned IP space ( http://192.0.34.120 ), but it does seem weird.

    The name servers handling icann.org (e.g. ns.apnic.net) also allow zone-transfers to all askers...Doesn't seem too secure to advertise the IP address for "jmb-laptop.icann.org", "hp4050a.icann.org", and other such presumably private names.

    These sorts of issues are (unfortunately) prevalent in the online world, but...c'mon, isn't ICANN supposed to be "dedicated to preserving the operational stability of the Internet"?

     
      ICANNWatch Login  
    Nickname:

    Password:

    [ Don't have an account yet? Please create one. It's not required, but as a registered user you can customize the site, post comments with your name, and accumulate reputation points ("karma") that will make your comments more visible. ]

     
      Related Links  
  • UDRP search page
  • http://192.0.34.120
  •  
    This discussion has been archived. No new comments can be posted.
    ICANN Network Bugs | Log in/Create an Account | Top | 5 comments | Search Discussion
    Click this button to post a comment to this story
    The options below will change how the comments display
    Threshold:
    Check box to change your default comment view
    The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
    Re: ICANN Network Bugs
    by PeterBarron (pebarron@hotmail.com) on Wednesday March 27 2002, @08:21AM (#5586)
    User #3240 Info | http://www.icannwatch.org/
    ICANN was supposed to be about technical coordination. These events, combined with years of similar occurrances, clearly shows that not only has ICANN failed in that they've been doing nothing but policy and corrupt management, but they cannot even handle their original mandate.

    It's time to take Stuart at his word that ICANN has failed, and not waste time with a restructuring. It's time for the ICANN contract to be rebid to an organization who will carry out the original task of technical coordination.

    ++Peter
    [ Reply to This | Parent ]
    Re: ICANN Network Bugs
    by fnord (groy2kNO@SPAMyahoo.com) on Wednesday March 27 2002, @01:35PM (#5600)
    User #2810 Info
    There doesn't seem to be any case D2002-9001, either in the 5* range or out.

    I wonder what the story is behind enetregistry.com (who's WHOIS can find itself but not icann.org or verisign.com). They've been around since '99, alternatively serving up 404 errors and claiming to be an ICANN accredited registrar, according to archive.org. According to this internic page they're accredited, but not according to ICANN's list. Lots of google hits showing them listed as an early registrar. In fact everyone but ICANN and apparently themselves seems to think they are a registrar. Perhaps that IP block is where registrars go when they die. -g

    [ Reply to This | Parent ]
  • 1 reply beneath your current threshold.

  • Search ICANNWatch.org:


    Privacy Policy: We will not knowingly give out your personal data -- other than identifying your postings in the way you direct by setting your configuration options -- without a court order. All logos and trademarks in this site are property of their respective owner. The comments are property of their posters, all the rest © 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008 by ICANNWatch.Org. This web site was made with Slashcode, a web portal system written in perl. Slashcode is Free Software released under the GNU/GPL license.
    You can syndicate our headlines in .rdf, .rss, or .xml. Domain registration services donated by DomainRegistry.com