>OK, however, are we completely sure that Chrome installer doesn't generate this token on launch and talk with the mothership? That wouldn't give any informati

>OK, however, are we completely sure that Chrome installer doesn't generate this token on launch and talk with the mothership? That wouldn't give any information about where/when you got the installer from, which is the topic of this article. Doing so would be impossible without embedding information in the exe (which would change the hash). While I agree that it's a little weird to specifically note it for Google of all companies, the relevance to the article is that Chrome isn't engaging in this specific type of tracking.