O popular navegador de internet Brave está próximo de receber o tão esperado recurso “tor over bridge”.
Resumindo, essa tecnologia te permite conectar na rede tor por meios alternativos.
Isso te dá 2 vantagens: contorno de bloqueio de acesso e o mais importante: mais privacidade.
Os links de acesso público ao tor são conhecidos por todos, incluindo governos e quem quiser te rastrar.
Porém, as bridges (pontes) servem para conectar no tor sem o uso desses links públicos, assim ninguém fica sabendo quando você acessa o tor.
O recurso é pedido desde 2018, mais de 3 anos atrás:
opened 12:24AM - 15 Sep 18 UTC
help wanted
feature/tor
priority/P3
We should eventually make it easy to configure advanced user-facing Tor features… like bridges and pluggable transports.
Acompanhe o desenvolvimento desse recurso aqui:
brave:master
← brave:tor_bridge
opened 11:52AM - 11 May 22 UTC
Resolves https://github.com/brave/brave-browser/issues/1138
## Sec review:
h… ttps://github.com/brave/security/issues/858
## Desc
1. Added a new component updater that handles the pluggable transport executables
2. Added support for configuring pluggable transport via Tor bridges
## Submitter Checklist:
- [x] I confirm that no security/privacy review [is needed](https://github.com/brave/brave-browser/wiki/Security-reviews), or that I have [requested](https://github.com/brave/security/issues/new/choose) one
- [x] There is a [ticket](https://github.com/brave/brave-browser/issues) for my issue
- [x] Used Github [auto-closing keywords](https://docs.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue) in the PR description above
- [ ] Wrote a good [PR/commit description](https://google.github.io/eng-practices/review/developer/cl-descriptions.html)
- [ ] Squashed any review feedback or "fixup" commits before merge, so that history is a record of what happened in the repo, not your PR
- [ ] Added appropriate labels (`QA/Yes` or `QA/No`; `release-notes/include` or `release-notes/exclude`; `OS/...`) to the associated issue
- [x] Checked the PR locally: `npm run test -- brave_browser_tests`, `npm run test -- brave_unit_tests`, `npm run lint`, `npm run gn_check`, `npm run tslint`
- [x] Ran `git rebase master` (if needed)
## Reviewer Checklist:
- [ ] A security review [is not needed](https://github.com/brave/brave-browser/wiki/Security-reviews), or a link to one is included in the PR description
- [ ] New files have MPL-2.0 license header
- [ ] Adequate test coverage exists to prevent regressions
- [ ] Major classes, functions and non-trivial code blocks are well-commented
- [ ] Changes in component dependencies are properly reflected in `gn`
- [ ] Code follows the [style guide](https://chromium.googlesource.com/chromium/src/+/HEAD/styleguide/c++/c++.md)
- [ ] Test plan is specified in PR before merging
## After-merge Checklist:
- [ ] The associated issue milestone is set to the smallest version that the
changes has landed on
- [ ] All relevant documentation has been updated, for instance:
- [ ] https://github.com/brave/brave-browser/wiki/Deviations-from-Chromium-(features-we-disable-or-remove)
- [ ] https://github.com/brave/brave-browser/wiki/Proxy-redirected-URLs
- [ ] https://github.com/brave/brave-browser/wiki/Fingerprinting-Protections
- [ ] https://github.com/brave/brave-browser/wiki/Brave%E2%80%99s-Use-of-Referral-Codes
- [ ] https://github.com/brave/brave-browser/wiki/Custom-Headers
- [ ] https://github.com/brave/brave-browser/wiki/Web-Compatibility-Exceptions-in-Brave
- [ ] https://github.com/brave/brave-browser/wiki/QA-Guide
- [ ] https://github.com/brave/brave-browser/wiki/P3A
## Test Plan:
Esse github está em constante desenvolvimento.
1 curtida