The problem is, if you require collaboration to get ANY coding done, you are a liability when you finally make it to the workforce. Some parts of coding, and engineering in general, need and benefit from collaboration; some don't.
doesn't change the fact that, in the rare case when something worthwhile is released, thousands upon thousands of normally law abiding netizens will choose to do the wrong thing.
Don't worry. They'll just change the name, and effectively ditch all the tar we've thrown on it. Look for the next version to more explictly address either terrorism, child porn, or drug kingpins. The RIAA/MPAA don't make very sympathetic/compelling victims. Got to spice it up a little bit.
There is a very good alternative to it all. Just walk away from it
Also known as the "take your marbles and go home" approach to political activism. Not very effective -- it's why we have things like the DMCA in the first place.
The A.ROOT is the master of them all. That's the one that they _really_ worry about, and the one referred to in that article (with all the security, etc.)
If it gets corrupted, even accidentally, the results would be disasterous. Although, I'm sure as soon as they realized it's been hosed, they'd cancel the next push (to the other root servers, keeping them "sane") and take the A.ROOT offline.
The A.ROOT is updated manually by Verisign engineers, after (I'm sure) meticulously checking the new database for errors. There's no room for a cronjob here. The database is generated on several other computers housed in that secure facility, compiling the changes from the various ICANN registrars around the world. Each registrar's changes are checked for consistency and compliance (the.au registrar can't change.com entries, etc.)
The other good thing about an attack like that is that the root servers dont rebuild there zone files and push that often.
no, no, no. You're missing the point.
If I compromise and poison D.ROOT-SERVERS.NET, it remains poisoned until the next push (twice daily). Anyone who does a DNS lookup, on average, refers to D.ROOT-SERVERS.NET once out of every 13 lookups, and therefore is subject to poisoning 1 out of 13 lookups. You'd never know, except when goatse shows up on your screen instead of microsoft.com;)
There is no system in place (at least, publicly known) whereby the root servers (or other major internet sites) compare the root servers' databases. They are simply trusted as "correct."
Poisoning the master (A.ROOT-SERVERS.NET) would be even more disasterous, since, on the next push, it would corrupt the remaining 12.
Similar end games exist for poisoning the trusted certifying authorities (root CAs) for RSA certificates. In the end, you have to trust something, and that something needs to be secure.
His comment was for DoS'ing the root servers, not compromising them.
If you DoSed up to 8 root servers (crashing them, overwhelming them with bogus requests, etc.) the remaining roots could sustain the load.
If you compromise a single root server, and poison its database, every single computer that looks up a hostname via that root server will be dorked. OK, so only 1 out of 13 of your DNS requests are poisoned...believe me, your surfing experience (think goatse.cx instead of cnn.com) will be "altered." Not to mention redirecting e-commerce traffic to trojan sites in order to capture passwords, credit card numbers, etc.
Slashdot Mirror
The problem is, if you require collaboration to get ANY coding done, you are a liability when you finally make it to the workforce. Some parts of coding, and engineering in general, need and benefit from collaboration; some don't.
pr0n
kazaa running in the background, with a dozen downloads in progress
do you also spray paint subways?
you, sir, are taking a huge slurp from the karma tit today. Congratulations to you! Cheerio.
who can't get the name of the copyright act correct, on a legal form no less. DMCA.
Again, nothing at stake here is something you're only now losing. You lost it long ago. Cheers.
If you really think anything the Connecticut DMV is asking for is something no one else in government already knows, well, that's cute.
Google runs on win2k, so in a way, Microsoft is helping you irregardless.
what?
BB needs to fix their customer service before they worry about fixing the rest of the world.
doesn't change the fact that, in the rare case when something worthwhile is released, thousands upon thousands of normally law abiding netizens will choose to do the wrong thing.
Nice try to get some WinKarma, you karma whore.
Linux users are still a negligible percentage of the consumer electronics industry.
And now, even Linux supports them, btw.
Winmodems are MUCH cheaper than the old style modems.
WinNICS will be too.
That's a bad thing? Linux will still support the old NICs, and eventually will support the new NICs.
Stop with the anti microsoft bullshit.
Actually, there's no arguing involved. Just submit your IP, and you're removed -- until the next time your mailer sends mail to the trap address.
Don't worry. They'll just change the name, and effectively ditch all the tar we've thrown on it. Look for the next version to more explictly address either terrorism, child porn, or drug kingpins. The RIAA/MPAA don't make very sympathetic/compelling victims. Got to spice it up a little bit.
It's being abused.
The model will be changed.
People will complain and say "we only did what you allowed us to do, why charge us more??"
The answer is: (1) because you ABUSED the service and (2) because you are costing us more money than you are worth.
People will claim that they have been shafted.
People like this are idiots. Selfish idiots, at that.
DSL will follow along in TW's footprints. Count on it.
It's their network. It's their prerogative, Bobby Brown. You pay, or you leave. Simple. Deal with it. Your "head in the sand" approach is comical.
They offer a service. They advertise that service. Some people extraordinarily abuse that service.
They CAN handle more users, it's just that these bandwidth pigs cost more than anyone else. It's called ROI. Look into it.
Also known as the "take your marbles and go home" approach to political activism. Not very effective -- it's why we have things like the DMCA in the first place.
The A.ROOT is the master of them all. That's the one that they _really_ worry about, and the one referred to in that article (with all the security, etc.)
If it gets corrupted, even accidentally, the results would be disasterous. Although, I'm sure as soon as they realized it's been hosed, they'd cancel the next push (to the other root servers, keeping them "sane") and take the A.ROOT offline.
The A.ROOT is updated manually by Verisign engineers, after (I'm sure) meticulously checking the new database for errors. There's no room for a cronjob here. The database is generated on several other computers housed in that secure facility, compiling the changes from the various ICANN registrars around the world. Each registrar's changes are checked for consistency and compliance (the .au registrar can't change .com entries, etc.)
cheers.
no, no, no. You're missing the point.
If I compromise and poison D.ROOT-SERVERS.NET, it remains poisoned until the next push (twice daily). Anyone who does a DNS lookup, on average, refers to D.ROOT-SERVERS.NET once out of every 13 lookups, and therefore is subject to poisoning 1 out of 13 lookups. You'd never know, except when goatse shows up on your screen instead of microsoft.com ;)
There is no system in place (at least, publicly known) whereby the root servers (or other major internet sites) compare the root servers' databases. They are simply trusted as "correct."
Poisoning the master (A.ROOT-SERVERS.NET) would be even more disasterous, since, on the next push, it would corrupt the remaining 12.
Similar end games exist for poisoning the trusted certifying authorities (root CAs) for RSA certificates. In the end, you have to trust something, and that something needs to be secure.
If you DoSed up to 8 root servers (crashing them, overwhelming them with bogus requests, etc.) the remaining roots could sustain the load.
If you compromise a single root server, and poison its database, every single computer that looks up a hostname via that root server will be dorked. OK, so only 1 out of 13 of your DNS requests are poisoned...believe me, your surfing experience (think goatse.cx instead of cnn.com) will be "altered." Not to mention redirecting e-commerce traffic to trojan sites in order to capture passwords, credit card numbers, etc.
The difference is: we TRUST the owners of the root servers to keep their systems secure. The owner's of KaZaA don't have the same track record.