Thread replies: 4
Thread images: 1
Thread images: 1
Anonymous
Brave Thread - Tor Tabs Edition 2017-08-26 08:55:46 Post No. 62102913
[Report] Image search: [Google]
Brave Thread - Tor Tabs Edition 2017-08-26 08:55:46 Post No. 62102913
[Report] Image search: [Google]
From the Brave github page. Firecucks and Chrome shills BTFO.
>All unencrypted (HTTP) connections are blocked by default, preventing attacks from malicious exit nodes.
>Javascript is disabled and fingerprinting protection is enabled by default.
>Each TPB tab uses a separate Tor circuit for requests originating from the webview in the tab. Requests originating from the main process related to TPB tabs (ex: URL bar search queries, favicon fetches, maybe websocket requests) should either go through a new Tor circuit or be blocked.
>No browsing data from TPB tabs should be written to disk.
>TPB tabs should not inherit state from regular tabs or vice-versa. This includes cookies, localStorage, cache, HSTS, etc.
>Browsing in regular tabs should not be affected, performance-wise.
>Plugins, extensions, and Brave Sync will not be runnable.
Can you imagine this?
>Browsing in regular tabs should not be affected, performance-wise.
Source:
https://github.com/brave/browser-laptop/wiki/Brave-Tor-Support
>>
>>62102913
>being that one single moron on the entire Tor network who uses Brave instead of the modified Firefox
I'm sure you'll be fine
>>
>>62102913
>fingerprinting protection
gonna need moar info on that one
>>
>>62103033
>>62103051
It's all in early development so not a lot of info at this point. Still great that they're considering this. Also >>62103033 one of their main devs works with the EFF and the Tor project so I'm sure there won't be major privacy issues.
Thread posts: 4
Thread images: 1
Thread images: 1