Update Brave HTTPS setting (#2247)

Signed-off-by: Daniel Gray <dngray@privacyguides.org>
This commit is contained in:
blacklight447 2023-07-24 15:27:07 +02:00 committed by GitHub
parent 2d0c5ea9a7
commit 821f35eb37
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -238,6 +238,7 @@ Shields' options can be downgraded on a per-site basis as needed, but by default
??? warning "Use default filter lists"
Brave allows you to select additional content filters within the internal `brave://adblock` page. We advise against using this feature; instead, keep the default filter lists. Using extra lists will make you stand out from other Brave users and may also increase attack surface if there is an exploit in Brave and a malicious rule is added to one of the lists you use.
- [x] Select **Strict** under **Upgrade connections to HTTPS**
- [x] (Optional) Select **Block Scripts** (1)
- [x] Select **Strict, may break sites** under Block fingerprinting
@ -258,7 +259,6 @@ Shields' options can be downgraded on a per-site basis as needed, but by default
- [ ] Uncheck **Allow privacy-preserving product analytics (P3A)**
- [ ] Uncheck **Automatically send daily usage ping to Brave**
- [ ] Uncheck **Automatically send diagnostic reports**
- [x] Select **Always use secure connections** in the **Security** menu
- [ ] Uncheck **Private window with Tor** (1)
!!! tip "Sanitizing on Close"