nikqwxq550

joined 1 month ago
[–] nikqwxq550@futurology.today 1 points 1 month ago

Lately they've been rate-limiting more heavily but if I wait and refresh enough times, or change circuits enough times, it tends to work

[–] nikqwxq550@futurology.today 2 points 1 month ago

It sounds like most other users install it that way too. Which surprises me, since I had thought the Linux community had started to move towards Flatpaks. But anybody who searched Flathub for Tor Browser, would have seen the flatpak with the Tor Project author listed as verified, and there would be no indication that this was in fact an unstable installation.

[–] nikqwxq550@futurology.today 2 points 1 month ago

I get what you're saying, but at the same time if every developer released software as pre-compiled binaries on their website, installing stuff on Linux would become such a PITA. (This is different from how Windows works because apps for Windows are distributed using installers like xxx.msi, and Linux does not have a unified installation system across distros)

[–] nikqwxq550@futurology.today 1 points 1 month ago (1 children)

You are right I should have linked directly to the workaround, sorry. Glad you got it sorted out though.

[–] nikqwxq550@futurology.today 3 points 1 month ago

the point of tor is not to avoid fingerprinting, it’s to blend in

Fingerprinting and blending in are the same thing. You can't blend in if you have a unique fingerprint. The Tor Project goes to great lengths to mitigate fingerprinting using their custom browser, it's one of their main goals. It's pointless to use Tor with a regular browser that doesn't have those protections, because websites can just identify you by your fingerprint even when you are obfuscating your IP using Tor.

You are no more tracked by Reddit than you would be with up to date tor

Browser version is a major part of your fingerprint. It's in your user agent, but that can be faked so there are additional mechanisms that check what javascript features your browser supports to get a more reliable read of your browser version. Use https://coveryourtracks.eff.org/ to learn more.

And fingerprinting is not a hack or exploit. It's something that websites use for tracking, just like cookies. And I'm almost certain that Reddit fingerprints users to detect ban evasions.

[–] nikqwxq550@futurology.today 3 points 1 month ago (1 children)

Wow nice. Still not really friendly to beginners, since this is something they would have to dig into documentation to find, but it's good to know

[–] nikqwxq550@futurology.today 2 points 1 month ago (2 children)

switch to the old.reddit.com site (onion version tends to work more often), and if that doesn't work, switch Tor circuits (the option is under Tor Browser menu bar, I have it pinned to the top-bar for convenience)

[–] nikqwxq550@futurology.today 21 points 1 month ago

This was an official Flatpak from Tor Browser, so there's no reason why it should be less reliable than the packages from distribution maintainers. Not to mention for atomic distros, flatpaks are the official way to install software.

[–] nikqwxq550@futurology.today 7 points 1 month ago* (last edited 1 month ago) (3 children)

You can check the Tor Project blog to figure out the latest release, and go to your Tor Browser's menu > Help > About Tor Browser to see if it matches. It should be version 14.0.7. If it is not, the fix is detailed in the Github issue I linked in the post

[–] nikqwxq550@futurology.today 4 points 1 month ago (4 children)

This seems like something that Flatpak should be able to handle though. Afaik Mullvad Browser never had this issue. Flatpaks also have numerous advantages, like automatically handling desktop shortcuts.

 

cross-posted from: https://futurology.today/post/4000823

And by burned, I mean "realize they have been burning for over a year". I'm referring to a bug in the Tor Browser flatpak that prevented the launcher from updating the actual browser, despite the launcher itself updating every week or so. The fix requires manual intervention, and this was never communicated to users. The browser itself also doesn't alert the user that it is outdated. The only reason I found out today was because the NoScript extension broke due to the browser being so old.

To make matters worse, the outdated version of the browser that I had, differs from the outdated version reported in the Github thread. In other words, if you were hoping that at least everybody affected by the bug would be stuck at the same version (and thus have the same fingerprint), that doesn't seem to be the case.

This is an extreme fingerprinting vulnerability. In fact I checked my fingerprint on multiple websites, and I had a unique fingerprint even with javascript disabled. So in other words, despite following the best privacy and security advice of:

  1. using Tor Browser
  2. disabling javascript
  3. keeping software updated

My online habits have been tracked for over a year. Even if Duckduckgo or Startpage doesn't fingerprint users, Reddit sure does (to detect ban evasions, etc), and we all know 90% of searches lead to Reddit, and that Reddit sells data to Google. So I have been browsing the web for over a year with a false sense of security, all the while most of my browsing was linked to a single identity, and that much data is more than enough to link it to my real identity.

How was I supposed to catch this? Manually check the About page of my browser to make sure the number keeps incrementing? Browse the Github issue tracker before bed? Is all this privacy and security advice actually good, or does it just give people a false sense of security, when in reality the software isn't maintained enough for those recommendations to make a difference? Sorry for the rant, it's just all so tiring.

Edit: I want to clarify that this is not an attack on the lone dev maintaining the Tor Browser flatpak. They mention in the issue that they were fairly busy last year. I just wanted to know how other people handled this issue.