Live data from Hacker News

Mozilla Project Fusion: Tor Integration into Firefox

trac.torproject.org

181–190 of 242 posts

Re: Mozilla Project Fusion: Tor Integration into Firefox

#181

Great news ! With wider adoption of ipv6 and all the good things that come with it (don't mistake me, they are great!) also comes the risk that each computer will get a uniquely identifiable IP address that will be used for fingerprinting. I've never really used Tor in the past, but this got me thinking about it. An option could be to provide a webRTC-based node, but I am not sure how feasible that would be, after re…

> An option could be to provide a webRTC-based node, but I am not sure how feasible that would be, after reading some comments here.

I'll point you at FlashProxy (https://crypto.stanford.edu/flashproxy/) and Snowflake (https://github.com/keroserene/snowflake) the latter of which is in active development. =)

Re: Mozilla Project Fusion: Tor Integration into Firefox

#182
post #30

Earlier quoted context omitted.

Honest question: is bittorrent even still a thing?

If you are asking about torrents and pirate community, then yes - it is alive and well. However it is usually through VPN, not Tor.

Torrenting through Tor overloads relays, increasing latency and throttling bandwidth for other users. Also, it's unworkably slow. Just use nested VPN chains.

Re: Mozilla Project Fusion: Tor Integration into Firefox

#183
post #174

Earlier quoted context omitted.

The risk now is that some bad actor is replacing TLS certificates, which is an uncommon and tamper-evident event. Tor is handing your traffic to an unknown 3rd party. Plus, users do not understand what Tor is or how to use it. Fighting political battles with software is dumb — the end result is going to be a permanent loss of freedom, as governments force the use of platforms with trusted app stores.

The risk now is BGP hijacking. Or really just normal operation of BGP. You data could go anywhere on the planet on its way to the destination and you're not going to know ahead of time what path any particular packet will take. If you're using TLS, it doesn't matter so much if the exit node is malicious because they still won't be able to read it.

How about my compromised browser exfiltrating information to an onion address?

Obviously I’m being downvoted into oblivion, but I truly feel this is a solution looking for a problem.

Re: Mozilla Project Fusion: Tor Integration into Firefox

#184
post #107

Earlier quoted context omitted.

How does this affect exit nodes?

If you're worried that law enforcement will knock on your door because somebody used your exit node for illegal internet activity, a VPN service (that does not log traffic) will give you additional protection by exposing their IP address, not yours.

A lot of VPN services forbid running exit nodes in their ToS as it tends to trash IP reputation...

Re: Mozilla Project Fusion: Tor Integration into Firefox

#185
I believe Tor browser is already just a version of Firefox if I'm not mistaken. What would be the advantage of integrating with Firefox as opposed to say, a VPN integrated into the browser via a plugin. Just seems a little redundant and Tor is beginning to seem dated also with new solutions popping up and making the pitfalls of Tor more apparent.

Re: Mozilla Project Fusion: Tor Integration into Firefox

#187
post #145

Earlier quoted context omitted.

> You can also run Tor relays and help us improve the health of the network by working with Tor's new Relay Advocate Since I've seen this come up before in many previous discussions of Tor I think it's worth emphasizing/clarifying up front: Tor relays are not the same as Tor exit nodes. Relays do not talk to the public internet, they serve only the full encrypted internal Tor virtual network. So they won't ever send…

That said, plenty of providers use the list of tor relays (which is also public) to block traffic. Sites such as https://www.dan.me.uk/dnsbl then help people do this. That site in particular may "warn": > This DNS blacklist contains ALL tor nodes (entry, transit and exit nodes) - think carefully before choosing to use this list for blocking purposes. but anyone who doesn't understand tor simply won't understand the d…

I had nothing but pain when trying to run an exit node. Every site behind cloudflair would captcha me on what seemed like every page. Cox shut off my internet every other week due to "computers on my network being infected with viruses", and I'd have to call their support and tell them I cant be infected I only run linux at home.

I could do some shenanigans on my modem and end up with a new dynamic IP from cox, but generally within hours that new IP would be on whatever list people use to track exit node IPs and the pain would start all over again.

Re: Mozilla Project Fusion: Tor Integration into Firefox

#188

I believe Tor browser is already just a version of Firefox if I'm not mistaken. What would be the advantage of integrating with Firefox as opposed to say, a VPN integrated into the browser via a plugin. Just seems a little redundant and Tor is beginning to seem dated also with new solutions popping up and making the pitfalls of Tor more apparent.

I imagine the idea is to have an incognito mode that actually is incognito, and free.

Re: Mozilla Project Fusion: Tor Integration into Firefox

#189

Earlier quoted context omitted.

I can't read this article because I'm at work, but unless they managed to solve the problem of Tor being very, very, very slow, this will never happen. End users will definitely notice a difference and likely won't care about their privacy. They'll just see Firefox being way slower than Chrome and switch.

This would be a privacy option for Firefox, not the default. But yes, Tor introduces latency and reduces bandwidth. For traffic to the open Internet, traffic uses circuits through three relays: entry guard, middle and exit. So there are four hops between users and websites, instead of one. The Earth's circumference is about 40 thousand km. So the longest path is arguably ~20 thousand km. And rtt for that would be abo…

So basically satellite Internet speeds. That is pretty good.

Re: Mozilla Project Fusion: Tor Integration into Firefox

#190

"Removing fingerprintability" amounts to the browser just NOT sending all the http request headers that it sends by default. How hard can it be to "comment out" these lines?

I just checked and there are over 100 checks for "should I have different behavior here if I am resisting fingerprinting?" just in the C++ code in Firefox today. There are some more in the JS code but they're harder to search for.

Some simple examples:

* Various navigator APIs (oscpu, platform, etc) need to be disabled.

* Gamepad API needs to be disabled.

* Have to prevent reading canvas pixel data

* Have to block information about avaiable OpenGL extensions from WebGL

* Modifier keys on keyboard events need to be spoofed (because they can be used to guess at keyboard layout)

* Errors from the media stack (for and ) need to be blanked out.

* Something to do with voice synthesis APIs; I didn't look into details.

* Connection API needs to be neutered

* Various timing APIs hanging off "performance" need to be neutered.

* Presentation API needs to be neutered.

* Number of CPUs reported by the navigator API needs to be spoofed.

* Window sizing for window.open needs to be spoofed.

* Ability to measure the difference between the window.inner* and window.outer* APIs needs to be disabled.

* Mouse positions in mouse events need to be spoofed to make it look like the window is fullscreened.

* Touch event positions need to be spoofed.

* Geolocation needs to be disabled.

And so on, and so forth.

Post reply on HN