What Could You Do With a Bogus Root Name Server?
Barlaam notes a post from the Renesys Blog which follows up on news they discussed a couple weeks ago about the 'identity theft' of a root name server. To emphasize the issue of safeguarding such a system, they've now posted an explanation of exactly how the situation could be exploited.
"It shouldn't be too hard to see that you could end up answering every DNS query from an organization that came to you for an updated list of root name servers. Every one. And you might end up doing this for a very long time, especially if your answers were largely correct. An attack like this would have no resemblance to the YouTube hijack, where the entire planet gets a blank page and it's immediately apparent that something isn't right. Obvious events like this will continue to occur, and we'll continue to resolve them relatively quickly. But as this incident demonstrates, DNS hijacks are far less obvious and potentially far more harmful."
.. do what we do every night.. try to take over the world!!
.... You could be cashing in big time..... )
(Seriously, Imagine borrowing every bank's front page in North America
i would redirect http://slashdot.org/ to http:///..org
yeah how funny is it now that the joke is on the other foot biatches!
intellectual property law is philosophically incoherent. it is your moral duty to ignore it or sabotage it
The solution is to maintain a series of flat-file or relational DBs locally for every host on the Internet. Periodically, you should be able to do an FTP or similar of the latest master file, and place it on your local nameservers or hosts. Its the only way to be sure.
I want to delete my account but Slashdot doesn't allow it.
It just doesn't scale. But you know that, don't you?
"Long run is a misleading guide to current affairs. In the long run we are all dead." (John Maynard Keynes)
Time for you mental midgets to start remembering IP addresses. Do your own damn cacheing.
It's a JOKE! Alright?
What?
You could send all Obama's web traffic to Clinton's web site ... oops, already been done!
1. Invest in sawdust futures. 2. Redirect everything to goatse.cx
Goatse.cx lives!
Have gnu, will travel.
Better, we can go on a strike and then shut down the Internet. Then, when governments of the world come to us asking for us to repair whatever happened, we say: "ok, we can do that, but before we do we need, 10 million dollars, 3 bikini supermodels and a fast sport car of our choice, for each one of us.
That would be sweet...
*GO BACK TO THE BASEMENT, JOHNNY*
*OK MOM! - Oh God, can't even dream in peace anymore...*
Chanting is clearly the network noise that p2p peers make simply letting other nodes know that they are alive and well (rather than traffic from transferring data or handling real business).
Nerd rage is the funniest rage.
Sir, what are you doing?!? Perl is NOT meant to be readable. It the code MUST be all on one line!
use strict; use warnings; use Net::DNS; my %hosts; sub lookup { my $res = Net::DNS::Resolver->new;my $query = $res->search( shift );if ($query) {foreach my $rr ($query->answer) {next unless( $rr->type eq "A" );return( $rr->address );}}else {warn "query failed: ", $res->errorstring, "\n";}}while( my $l = ) {if( $l =~ m!(http://.+?)\s! ) {print( "$1\n" );if( $1 =~ m!http://(.*?)/! ) {my $ip = lookup( $1 );$hosts{$1} = $ip;}}}foreach $host ( sort keys( %hosts ) ) {print( $host, "\t", $hosts{$host}, "\n" );}
There, fixed it for ya!