Self-negating advice on privacy

This suggestion from LifeHacker is unlikely to work. First it’s not all clear that the DNS names in question are affiliated with Google. The mappings can change and sending search-queries to random third party is hardly conducive to privacy. Second the threat model assumed here is a lost cause. Most enterprises control the computing environment used by their employees, right down to the software for web browsing. That means web history can be ferreted out of the client side, without having to sift through proxy logs or network traces. (Home user vs. over-reaching ISP is a better example.)

But there is another reason for the overwhelming futility of the idea: even if it were useful against the current crop of Big-Brother-ware because of an oversight in the URLs it logs, publicizing that blind-spot only ensures that the next versions are likely to fix the problem.


Leave a Reply

Please log in using one of these methods to post your comment: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s