Developers warning: A bug in the new version of Google Chrome could leak the identity of the users who surf anonimously. (Via TheRegister.co.uk)
The problem is regarding the proxy settings in Chrome. Basically when you set up a proxy, all the traffic that is made by an IP is hidden by the proxy server, but Chrome will connect to the webpages through the users’ local network, so the anonimity settings won’t work.
“This presents a serious risk for the users of the services such as Tor, as their DNS data and the little anonymity they have with Tor is leaked outside and in the clear,” according to an advisory published Monday on the Full-Disclosure mailing list.”
Tor stopped working on Chrome 3.0.195.33. Tor used to connect to a webpage through someone’s IP from the Tor network, but Tor functionality is disabled in the newest version of Chrome.
Around the participants to Chrome’s open-source code, some say that this security risk exists because of something called “DNS pre-fetching”, but others say that the security risk is available even if the DNS pre-fetching is disabled.
The time when this security breach will be patched is unknown, for now.
“We’re looking into fixing this issue,” a Google spokesman said, “but it only potentially impacts a very small number of people who make use of anonymity services like Tor.”
What do you think of this problem? Are you one of the small number of people that are using Tor? 
Loading ...
One Comment
I used to use tor via xb browser, but due to it looping when started I quit it.Don’t have google chrome install on my computer because I believe that browser is the opposite of privacy,funny thing I was reading on wilderssecurity about xb machine is beta testing using chrome,hope this don’t become an issue in vpn.