You had to make sure that you didn’t have browser plugins like Flash or Java enabled that would compromise your anonymity. In the past if you wanted anonymity you had to download and install Tor, maybe hand-edit your torrc file, and configure your browser to use a proxy server. Over the years, Tor Project has done an amazing job at making Tor more user-friendly. I’d like help finding bugs before the initial release. I'll try to find and test older versions of Tor next.TL DR: I wrote a piece of software called Tor Browser Launcher that downloads and auto-updates Tor Browser Bundle for you, in your language and for your architecture, and verifies signatures. (Note that CIS does not (and apparently cannot) disable Windows Defender Firewall.)įWIW, I tested several more browsers in the Container and they worked OK: Brave, Chrome, IceDragon, Maxthon, SeaMonkey and Vivaldi.
I don't know why this is a problem only when Tor is run in Comodo's container, though.īut Tor v11 (both stable and alpha) still doesn't work in the container. Its log also claimed traffic from Tor on that port was getting through. I also added a rule to Comodo's Firewall to explicitly allow traffic in and out on that port, although that probably wasn't necessary. Windows Defender Firewall's log file then claimed that it was getting through.
I created an inbound rule and an outbound rule to allow that traffic. I suspect other network related programs do, too. The Tor browser uses the localhost address. The log file didn't show any other traffic being dropped. I enabled Windows Defender Firewall logging and discovered that it was dropping both inbound and outbound traffic for the IP address 127.0.0.1 (localhost)
A problem found, but Tor browser v11 still doesn't work:
0 kommentar(er)
