Silk Road forums

Discussion => Security => Topic started by: TravellingWithoutMoving on May 02, 2012, 10:17 pm

Title: Success - Tor button/vidalia & google Chrome?!
Post by: TravellingWithoutMoving on May 02, 2012, 10:17 pm
hello

anyone got this working....any good?!

TWM
Title: Re: Success - Tor button/vidalia & google Chrome?!
Post by: TravellingWithoutMoving on May 02, 2012, 10:27 pm
...found this post...not folowed the steps...
http://dkn255hz262ypmii.onion/index.php?topic=254.msg1669#msg1669

Title: Google Chrome Incognito Mode, Tor, and Fingerprinting
Post by: TravellingWithoutMoving on May 02, 2012, 11:00 pm
https://blog.torproject.org/blog/google-chrome-incognito-mode-tor-and-fingerprinting
Google Chrome Incognito Mode, Tor, and Fingerprinting

A few months back, I posted that we have been in discussion with Mozilla about improving their Private Browsing mode to resist fingerprinting and the network adversary. As I mentioned there, we have also been doing the same thing with Google for Google Chrome. Google has taken the same approach as Firefox for their Incognito mode, which means that it provides little to no protections against a network adversary.

This means that Chrome Incognito mode is not safe to use with Tor.
The Story So Far

In general, Incognito's major shortcomings are plugins, fingerprinting, DNS leaks, SSL state leaks, auto-formfill and site-specific zoom. The Applied Crypto research group at Stanford recently published a comparison of the four major browser's private browsing modes against a dedicated local and remote adversary which details some of these issues. The added poison for Tor is that plugins and DNS leaks can also reveal your IP address and complete web activity to the network adversary.
. . .
. . .
Title: Re: Success - Tor button/vidalia & google Chrome?!
Post by: pine on May 03, 2012, 01:09 am
I'm happy with my fox.
Title: Re: Success - Tor button/vidalia & google Chrome?!
Post by: TravellingWithoutMoving on May 04, 2012, 08:24 pm
- in summary there seemed to be outstanding bugs with either chrome, chrome + Tor implementation, and / or progress on this seemed to stop
  abruptly 2009/2010 so my guess is DON'T TRY USE CHROME & Tor, too much of a security risk etc.
  So i assumed they abandoned trying to get it working...