SoylentNews

Gabe Newell Responds to DNS Snooping Allegations

posted by Dopefish on Tuesday February 18 2014, @05:00AM   
from the move-along-nothing-to-see-here dept.

Lagg writes:

"We're in a climate where it's easy to accuse a company of spying on you by various means with a distinct possibility that you could be right, but sometimes a reality check is needed. A Reddit user recently posted a thread accusing Valve of writing code for VAC that iterates your DNS cache and sends the hashed entries to their server. The proof provided of this was a prettied disassembly (that was not easily reproducible due to how VAC loads symbols) that showed only that VAC was indeed iterating the DNS cache, which any knowledgeable programmer understands is not exactly an uncommon thing to do, as no socket code was to be seen. Today, Gabe Newell responded to these allegations by confirming that no they do not in fact snoop your cache entries.

There are probably a few things to learn from this, including not trusting a screenshot of code that looks complex without actually understanding what it's doing. A lack of any level-headed investigation is a bad idea and it's important to handle these situations before they snowball into a mob (as Redditors are bound to do)."

• Re:Please explain (Score: 1) by Lagg on Tuesday February 18 2014, @03:42PM

  by Lagg (105) on Tuesday February 18 2014, @03:42PM (#1657) Homepage Journal

  Sorry for that. I should have explained. It's a micro-optimization sometimes used when the code needs to do a lot of resolves to a small set of names. I'm not going to vouch for the usefulness of it, but it is done. Particularly in environments where the overhead of repeated resolve calls is not wanted or needed, like in embedded stuff. I guess bypassing the resolver entirely can help to a degree in those situations, but it's not needed much in today's systems in my opinion. It all comes down to whether or not you think that the overhead of your given resolver lib is worth working around after the initial query to the nameserver. Basically, you implement such a thing when you think you can do the caching better. When I first saw this thread I didn't think it too out of the ordinary since goldsrc was based on quake's engine and there could very well be such code leftover that is shared with other stuff. Since iD loved to do these kind-of-silly-even-for-the-time micro-optimizations it kind of made sense. If you've worked with net code before you've probably heard of this more than you think.

  --
  http://lagg.me [lagg.me] 🗿

  Parent