When the Internet Nearly Fractured
An anonymous reader writes "The Atlantic has a fascinating, if lengthy, story about a man named Eugene Kashpureff who 'ignited a battle over the future of the global network' by launching a rogue DNS registry in the late '90s. Here's an excerpt: 'He opted to go a step beyond simply registering sites on alternative top-level domains, and hijacked traffic intended for InterNIC.net. He pointed the domain to his own site, where he lodged a note of protest over how the domain name space was being controlled, and then offered visitors the option of continuing on to Network Solution's site. This was, you'll recall, at about the same moment that the federal government was attempting to make the case to the business community, to the world, that this Internet thing was no digital Wild West.'"
Eugene Kashpureff was a man who not only saw future threats to the freedom of internet in 1990s, but also someone who had the guts to do something about it ?
we need more Kashpureffs on this planet. many, many more.
Read radical news here
Teh Google is to blame !!
I totally know this guy. He used to teach classes for the company I work for. Weird.
The internet poses two possibilities:
1. It is a haven of freedom and anarchy.
2. It is a tool for social control.
It is amazing that, for example, police are furious that people can encrypt their internet communication. Shouldn't police have a super-key to let them track down criminals? But it never occurs to them to ask for a super-key to let them spy on everyone's secret in-person conversations. Oh wait... yeah, they want that too.
The forces of institutionalized government tend to inherently become the forces for totalitarianism (unless there is some kind of complete direct democracy). So we are at a crucial juncture in history right now.
Do we let the internet become the ultimate tool for our suppression, or the ultimate tool for our liberation?
I must admit that I haven't RTFA. But the summary quotation seems to imply that DNS is somehow part of the Internet.
Just to clarify, it's not. The internet sure would be hard to use without the DNS, absolutely. But it's not unthinkable - we'd just be stuck with IP addresses for everything, and there could be no virtual hosting (multiple domains per IP, disambiguated by the Host: field).
But the DNS is really more of a universal agreement. Everybody agrees on who the roots are, and that's that. But there's no technical reason that the roots have to be who they are - hence the altroots described.
But he didn't "fracture" the Internet. That's a stupid statement. The Internet doesn't concern itself with domain names, just routing IPs - the DNS is built on top of that and maps back down to IPs. Were he successful, he would've fractured the DNS. Pain in the ass? Sure. Coke.com could go to Pepsi's site, but http://216.64.210.28/ would still get me to the Coca-Cola website.
The difference matters, because fracturing the Internet is technical (routing), while fracturing the DNS is more of an administrative-bureaucratic-sociopolitical type of thing. Peering disputes can of course be about non-technical things like money, but it breaks at a technical level.
I have developed a truly marvelous proof of this comment, which this signature is too narrow to contain.
"When all this is over, we want this guy to get a medal. Then we want him locked up."
.
Prisencolinensinainciusol. Ol Rait!
Splintering DNS forks the Internet so that Internet users might never know where to go to get domains, or what they might get.
Which is worse: Injecting forged data into the DNS, or eliminating data that you don't like?
Kashpureff was guilty of the former. Now the US government is doing the latter - seizing domain names on behalf of commercial interests.
With corporate interests pushing governments to use domain name forfeitures to punish people/groups it finds threatening to their interests, it will cause people to create new name services.
He hacked people's servers (including some belonging to the DOD) and went to jail for it. When I pointed out that my non-hacked DNS servers couldn't see the Alternic domains, he hacked those too.
For some reason, top level domains have the ability to bring out the crazies. It happened in the late 1990's, and it's happening again (e.g., with .music).
>>> 4,000-line HOSTS files like I used to back in 1983,
Size Matters
Mine is 19,046 long.
Wow, don't think something like that would ever happen again
Wonder when someone will come up with a distributed peer to peer type of setup as an alternative to a central authority.. Or is there something like that already?
We outgrew hosts files.
We've outgrown DNS as well.
Take a look at .COM for example. DNS is now basically flat, despite the original intent. .COM is a great big flat hosts table.
DNS is an attempt to categorise networks, companies, services etc. .COM for commercial, .US for American, .ORG for non profit organisations, .PRO for professionals (LOL). The problem is it's hierarchical, and categorising all the people, services, networks companies in the world doesn't work in a hierarchy. I need to be in .DE, .PRO, .NAME, .CO.UK etc. Duplication of information. People have just decided to use .COM instead and include some keywords in the name. It's simpler.
Naming, classification is relational rather than hierarchical. We need a replacement name resolution service. DNS will continue to creak under the inappropriate uses we put it to day.
Deleted
It's important to remember that when he did this, he was essentially fighting against the mandated monopoly on domain registration held by Network Solutions. At that time, the domain registration process had all the speed efficiency, charm, and conscientiousness as the DMV on a bad day. Meanwhile, we had several prominant cases where exceptions were made to the first come first served policy to give privately held domain names to corporations that want them even when their trademark was newer than the original registration.
At the height of that Kashpureff partially hijacked DNS for a little bit to raise awareness of alternatives.
The issues from then were partially addressed by opening up competition in domain registration and further by regulating the dirtier practices of registrars.
I guess if it is longer than a tweet, it's too long.
you should read everything on the internet as if it had "but I'm probably talking out of my ass" appended to it.
And then it was. True story.
Old news, slashdot. Very old news!
tl;dr pls sum.<=140 char
a "fractured internet" is bad for the network, so if it ever came to that it would just mean typing:
tech.slashdot.org.internic
if you wanted to ensure you were being unambiguous. It really would not have been the end of the world.
-- 'The' Lord and Master Bitman On High, Master Of All
i totally forgot! they were fun ... for two days.
really it was supposed to be a revolution/ riot thing. but i think it was so little of a nucance ot had virtually no impact. nothink like cutting internet for an entire country(a nucance that luckyly backfired spectacularly).
The funny mods seem deserved, but this seems like the little detail you'd look up specifically for purposes of giving it as an example.
I listen to both RIAA and non-RIAA stuff if I like the music, tangential business/politics nonwithstanding.
As far as I could tell from the outside, the big objective of ICANN was to give the Trademark Gods more control over the domain-name process than they were going to get through the IAHC, and to prevent new top-level domains from happening, and I was already annoyed at the IAHC for being too subservient to the Trademark Gods. The big issues for me were getting more gTLDs created and making sure that the domain name process could preserve privacy, while the IAHC had pretty much agreed that you wouldn't be able to get a domain name without providing your True Name and ICBM\\\\Lawsuit Address.
Unlike some people, I didn't mind that the Ad-Hoc Committee's first seven domain names were pretty lame and boring - it's a process the world only gets to do once, so it's a lot better to practice it on namespaces nobody cares much about like .FIRM and .NOM, so they can do the job right for more valuable names like .INC, .GMBH, .LLC, .SA, etc. But the takeover by ICANN prevented even those from happening, so we end up with a flat cluttered .COM namespace instead of a more complex and meaningful one.
ICANN accomplished a few more things for its friends in power along the way - delaying DNSSEC and to some extent IPv6, and making it much harder to do experimentally-structured namespaces (with the exception of .museum, which was interesting.) Some things I'll ascribe mostly to incompetence rather than malice - because they really didn't want new TLDs, they didn't do any research into non-7-bit namespaces, so by the time the international-language crowd put enough pressure on them to Do Something, they adopted the appallingly-broken Punycode stuff (which I think came from NetSol, but I could easily be wrong about that.) I was especially annoyed that they asserted control over the IPv6 namespace, because fundamentally they care about Intellectual Property, not the Internet Protocol, and they made it hard for people to get official space for research purposes by charging a lot for it, as opposed to carving up 1/256th or 1/4096th of it and saying "it's experimental, go play with it, have fun!"
Bill Stewart
New Fast-Compression-only CPR http://preview.tinyurl.com/dy575ks
There was a short period of time that almost 1% of the Internet's users could use Kashpureff's root in addition to the real one, but nobody serious was going to pay significant money to only be in Alter-space and not real space. Sure, you might pay $10 to register example.xxx, if example.com had already been bought, but it was obviously a losing deal.
Bill Stewart
New Fast-Compression-only CPR http://preview.tinyurl.com/dy575ks
"We outgrew hosts files." - by Colin Smith (2679) on Friday February 25, @02:22PM (#35315548)
HOSTS files are still QUITE useful, especially in conjunction w/ DNS... I rotate between OpenDNS, ScrubIT DNS, Google DNS, & Amazon DNS servers.
I use HOSTS files for these purposes:
---
1.) Blocking out adbanners for BOTH added speed ( & it's QUITE noticeable, doubles my speed online on the web in fact I'd say, AND for security - since adbanners have been shown to bear malicious code in them MANY times now the past decade).
2.) Hardcoding 250 of my favorite website into it for both extra SPEED, and RELIABILITY (to avoid the time taken to DNS roundtrip resolutions, and, to avoid DNS "poisoning/misdirection/redirection" attacks, & to my favs especially - so, even if the DNS is downed, or hijacked in any way, I still get to my fav places online - reliably (and I ping them regularly via a program I wrote to do so to automate it)).
3.) Blocking out KNOWN bad sites/servers/hosts-domain names, for security vs. malicious sites (up to nearly 937,000 of them currently) - for "obvious reasons" here (security & staying free of malware in general etc.)
---
They work for those purposes, like NO TOMORROW... very effectively, & I'm FAR from "alone" in using them this way (think mvps.org for example)...
APK
P.S.=> In fact I find HOSTS files to be superior to browser addons like adblock (especially adblock alone), because HOSTS cover you "universally" across any & all apps that use the web... including browsers adblock doesn't cover, & external-to-browser email programs like Outlook Express/Full Outlook & others also... good stuff! apk
...isn't the Internet this internet explorer thing, I mean WWW?
(sorry, just couldn't resist)