They fixed the bug when it was reported on GitHub.Īccording to you, why did it happen? Are you insinuating that the ISPs or the state were paying Brave Software to introduce the bug? That’s called a conspiracy theory, my main man, and is not really consistent with them fixing the bug immediately upon hearing of it. So they were entering new territory here, and this can produce bugs. The bug causing the leak was introduced when they implemented CNAME uncloaking for Brave Shields, a feature which no other Chromium-based browser has.
So my response to this is: Who cares? If you know about Tor then you know about fingerprinting, and that Brave does not have the same FP as the Tor Browser Bundle. I don’t have to justify features that are used only by a minority of Brave users, actually I don’t use the Tor mode either. You act as if the Tor mode is Brave’s main selling point, LOL. > Now the brain tease: Why even offer a TOR mode if it is broken? Brave actually says to use the TBB if you want to do more than hide your IP address, right when you enter Brave’s Tor mode. So even when Brave’s Tor mode hides your IP address, it does not have the common fingerprint of the Tor Browser Bundle. Uhm… yeah? What is the controversy here? A browser using Blink can’t emulate the fingerprint of a browser using Gecko and vice versa.
While there was an option to modify the behavior by enabling "always ask you where to save files" in the preferences, it did not replicate the full functionality of the classic download prompt. The new download prompt copied the behavior of Chromium-based browsers this meant that Firefox started the download immediately. Mozilla changed the download behavior of the browser in Firefox version 97, which it released in January 2022.įirefox used to display a prompt to the user, giving them options to open or save the file. The big new improvement in Firefox 101 is one that is not highlighted in the official release notes.