Slashdot Mirror
US .gov WHOIS Info Restricted Over Attacker Fears
An anonymous reader writes "VeriSign Inc has stopped providing access to information about the .gov internet domain, which is restricted to US government bodies, over concerns the data could be used in planning internet attacks."
C/O George W. Bush
1600 Pennsylvania Avenue
Washington, DC.
Yup, wouldn't want anyone to know where HE lives, do we?
/^[A-Z0-9._%+-]+@[A-Z0-9.-]+\.[A-Z]{2,4}$/i
If you need whois data for a ".gov" domain, go to the General Services Administration.
sarchasm: The gulf between the author of sarcastic wit and the person who doesn't get it.
There shouldn't even be a .gov TLD.
.gov.us
It should be
...hide the contents of the websites too?
Not much point hiding the whois information of a domain if its accompanying website tells the whole world who and where they are...
-- Even if a god did exist, why the fsck should I worship it?
I think they should restrict access to the .gov DNS records also. Would go a long way in making the .gov net a whole lot more secure. :)
It had to be a matter of public record anyway, right? I don't see what this solves. I think the old term "Security throught obscurity" applies here. That term has also been trampled on time and again because it just doesn't work. Hide information via one source, get all confident that you're safe, and then get surprised when you're actually not.
Is there anyone out there who can explain what this accomplishes really? I'm seriously asking because I might be missing something.
Luck favors the prepared, darling.
While I think the intent is admirable, the net effect might be somewhat frustrating. For example, how are we supposed to get contact info if say a governement group's DNS goes south? Or maybe just a portions of it? what about entities that have been misapportioned? (Good example is the City of Albuquerque, NM.)
The quote that I found interesting is: "Also removed from the FTP site was the zone file for in-addr.arpa, which is used for reverse-DNS lookups (when somebody wants to find out what domain is associated with an IP address, rather than the other way around)." So is this a prelude for them to stop supporting rev. DNS? If it does stop, are they really aware of the potential consequences? (Stopped email, blocked access, etc.) What about who to contact and how to contact them about possible network outages?
Things like this might seem like a good idea at the time, but can (and do) lead to other problems. I am in favor of security as much as the next guy, but half though-out moves like this don't help.
-D.
P.S. I wonder if they are going to stop publishing things like the white pages (online or even the print edition)? Hey they do have government entity addresses and phone numbers?
I wonder whether .gov will find itself listed in
on rfc-ignorant
for this.
Prime numbers are exactly what Alan Greenspan says they are -S. Minsky
You damn pot smoking Californians need to realize CA is not a country (as much as you wish it were).
.ca domain YOU HAVEN'T WON YET. I'm looking forward to .TX for Texas to leave the Union (and take GW with them).
Just because you somehow tricked the powers that be into making a
If you want to participare in a public network then they shouldn't be hiding whois information. Nobody is saying they can't run their own top secret nework (as I'm sure they already do to some degree) but participation in this giant public network involves some amount of conformance to standards.
Any information that is so critical to national security shouldn't be on the internet in the first place.
- Toby