[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: Firefox IPv6 Anonymity bypass

Greetings and welcome to 2006!


Excerpt from "How To Create Torpark"

Step 31. set as follows:
    noscript.notify.hideDelay = 30	
    noscript.statusIcon = false
    network.dns.disableIPv6 = true ; ipv6 addresses fail through tor.
    network.proxy.socks_remote_dns = true
    browser.sessionstore.enabled = false
    browser.sessionhistory.max_entries = 1
    network.cookie.lifetime.days = 0
    dom.storage.enabled = false
    dom.max_script_run_time = 60 ;script running time
    dom.max_chrome_script_run_time = 60;
    network.proxy.failover_timeout = 0 ;always retry the proxy, never
    plugin.scan.plid.all = false ;Do not allow plugin scanning.
    security.xpconnect.plugin.unrestricted = false; do not allow
unlimited access to XPConnect
    layout.css.report_errors = false ;get rid of java console errors

Kyle Williams wrote:
> Nice find!
> Thanks for reporting it.
> On 10/25/07, Nick 'Zaf' Clifford <zaf@xxxxxxxxx> wrote:
>> Hey ya,
>> Just noticed one small problem with Tor + Firefox + IPv6.
>> I'm aware that Tor doesn't yet support IPv6, but I found an interesting
>> development with respect to a system that has IPv6 configured and working.
>> If you are using Tor (and have Firefox configured to use the HTTP
>> proxy), Firefox will not use the proxy for IPv6 traffic. This means that
>> if you visit a website using Tor, and it has a img, href, etc to a ipv6
>> hostname, Firefox will happily connect with your native IPv6 connection
>> (bypassing Tor).
>> The work around for this is to disable Ipv6 (about:config,
>> network.dns.disableIPv6 = true)
>> I guess this is a bug with Firefox rather than Tor, but it should be
>> noted in a wiki somewhere, as IPv6 is becoming more and more prevalent
>> and networks are becoming connected. It is of great concern for those in
>> China, where IPv6 is being rolled out at a great rate of knots.
>> Nick