Stealing the United States Government by stealing .gov
breaksecurity.com
breaksecurity.com
As part of this, Cyberdyne Systems will be running .gov-wide grid services in the background on the .gov hosts, so please ignore the skynetd daemon that will now be running on your servers.
But seriously, this is how outsourcing and privatization works. It's how Xe Services is an extension of the military, how Corrections Corporation of America runs private prisons, the Kelo case in Connecticut, the 1% claims settlement between BofA and Fannie Mae, and other cases of privatization.
The government does what the population and the corporations ask of it, and the private entities then provide the rest of the services on behalf of the government; it's how government itself gets outsourced.
And yes, government-outsourcing makes following the accounting and the budgets far more difficult. You just don't easily know how big a military effort might be without finding those other line items in those other budgets, for instance. Or when some private entity effectively holds the keys to some large tract of government services or security.
Little note: this is what Blackwater is calling themselves these days. I didn't know this, and figured I'd save someone from looking it up.
"We are a professional organization serving as a solutions provider to the U.S. government."
No doubt.
So basically he just took back everything he wrote before that update.
Derek and I had a good talk on the phone and some things I brought up are that if the domain usadotgov.net does get hijacked and the person does fiddle with things it could cause some issues if you are using a non-verifying DNSSEC resolver (not only this but .net domains can’t be signed at the registry yet) but the question becomes does the resolver go to the root or the .net for the information for a.usadotgov.net and do all resolvers work the same. What he was trying to convey is that since the records are signed and the government uses verfying resolvers there should be no issues.
I also brought up the fact that a country could send back spoofed records from the root servers as has happened before. If I can spoof a.usadotgov.net and look like I’m answering from l.root-servers.net then what happens. Hopefully this will all go away as DNSSEC is more widely deployed.
Update 3
I asked Paul Vixie the question below as I didn’t want to keep going back and forth on the issue.
“I guess my question is what happens to .org is usadotgov.net is hijacked, what damage can truly be done.”
His reply:
Such a hijacker could make any .gov name say anything they wanted it to say, as long as the software looking up the bad data wasn’t dnssec-aware.
Incidentally mod.uk has a nameserver pointing to ns1.cs.ucl.ac.uk. I wonder if there are many other domains that use academic resources.
I would probably trust them to get it right more than whatever nominet are calling themselves today
$ dig +short ie ns
ns3.ns.esat.net.
gns1.domainregistry.ie.
uucp-gw-1.pa.dec.com.
ns-ie.nic.fr.
uucp-gw-2.pa.dec.com.
banba.domainregistry.ie.
gns2.domainregistry.ie.
b.iedr.ie.
ice.netsource.ie.
Up until about 2004, domains here in Ireland were being sold for extortionate amounts of money compared to other TLD's (100 euros a pop from the registry). There was some scandal regarding the body running the registry and the head of the body Michael Fagan was essentially forced to resign circa 2002But then, the thought probably never occurred to them.