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.

  • lemel@lemmy.mlEnglish
    0·
    2 hours ago

    How do you even access Reddit from Tor? I always see the message saying that my attempt was blocked by “Network Security”.

    • corsicanguppy@lemmy.caEnglish
      0·
      2 hours ago

      The only thing they offer is bare source?

      I like they’ve just given up on trying to understand things like filesystem layouts and fucking systemd - which is cool - but now they own dependency hell and inconsistent installs in trade.

      Nah. I’ll get a package where I can confirm the contents, check the sigs, reproduce the build and then deploy it with its dependencies in a reliable, verifiably-consistent process.

      https://rhel.pkgs.org/9/epel-x86_64/tor-0.4.8.14-1.el9.x86_64.rpm.html

      Sources, sigs, signed BoM. Wheeee!

  • bad_news@lemmy.billiam.net
    0·
    6 hours ago

    Tor “installed” via non-flatpak updates via the same manual mechanism, so it’s no worse than the non-flatpak. The flatpak is just the installer. Also, the point of tor is not to avoid fingerprinting, it’s to blend in. You are no more tracked by Reddit than you would be with up to date tor. A publicly traded company is not going to actively try to exploit your browser with a hack to fingerprint you extra via an exploit. You should never use tor for 1-1 you things comingled with anything you don’t want associated with you. That’s why there’s an easy to use new identity button. Tor is not magic, its on YOU to engage in best practices or not.

  • narc0tic_bird@lemm.ee
    0·
    10 hours ago

    Why don’t they bundle the browser itself in the Flatpak and update it via the default Flatpak update mechanism?

  • muhyb@programming.dev
    0·
    12 hours ago

    Well, for Tor Browser even AUR isn’t recommended. Just download it from official website and put it under somewhere like ~/.local/opt.

    • nikqwxq550@futurology.todayOPEnglish
      0·
      9 hours ago

      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.

      • Asparagus0098@sh.itjust.worksEnglish
        0·
        3 hours ago

        I’d like to add that you can setup desktop shortcuts pretty easily for Mullvad and TOR browser manual installs. For TOR browser simply run this after opening a terminal in the folder it was extracted to:

        ./start-tor-browser.desktop --register-app

        Same thing should work for mullvad.

    • nikqwxq550@futurology.todayOPEnglish
      0·
      9 hours 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.

  • Vincent@feddit.nl
    0·
    12 hours ago

    So… How do we do we’re running an outdated version, and what is the fix that requires manual intervention?

      • Vincent@feddit.nl
        0·
        7 hours ago

        It was collapsed for me at first, and buried under a lot of other comments, but a workaround is mentioned here. Unfortunately, that didn’t seem to work for me, but deleting the Flatpak and deleting all associated data, and then reinstalling it, I think did the trick.

        Although it does now show this warning, which doesn’t sound great.

        Edit: actually, I think that was the reason I concluded the first workaround didn’t work, but looking at that URL, this might just have been introduced in Firefox 128, which is newer than the old version of Tor was based on. So it looks like both worked.