Comment #19 on issue 469 by ioerror: Support SOCKS proxy http://code.google.com/p/chromium/issues/detail?id=469
I think that it's important not to settle for plain SOCKSv4. SOCKSv4 has a few disadvantages, an obvious one is DNS resolution. With SOCKSv4, DNS resolution will happen through the local network rather than the remote SOCKS endpoint. SOCKSv4a or SOCKSv5 would allow Chrome users to use a SOCKS proxy without DNS leaks. SOCKSv5 also allows for many more types of authentication with the SOCKS server. SOCKSv4a is probably easier to implement and is a good middle ground. (As a disclaimer, I'm a Tor developer. Also, I'm hopeful that we can use Chrome and Tor together someday without leaking information to the local network.) -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
