1
0

Consideration closing the project #1

Open
opened 2024-08-22 15:11:38 +02:00 by CHEF-KOCH · 0 comments
Owner

The project is more or less obsolete, Brave or Chromium added my suggestion to display the default state of the flags among a small info if the current settings is the default or not.

The main goal was to harden the Browser to make it less vulnerable, less fingerprintable as well as overall more secure. Brave already now provides a reasonable secure and private Browser, which do not needs to be hardened anymore.

The only suggestion someone can provide is to use xyz personal preferences which you can use, or not use, in the settings. However, most of those settings are not related to privacy or security at all - even tho it is misconstrued as such - e.g. turning off the wallet function to avoid connections to their services, when the reality is much different because connections are - in this example - only made when you actually try to use such a feature and they are NOT constantly established when you NOT use this, in other words, leaving such toggles as they are, in their default state, even if they are enabled are not related to privacy implications at all unless someone provides reasonable evidence that this is not the case, bugs etc. aside of course.

That said, thanks for the ride. I am closing this project, thank the Chromium as well as Brave developers to enhance the default settings as well as the flags and their description.

I have no plans to change any of the flags myself anymore which means that this the end of the project.

The project is more or less obsolete, Brave or Chromium added my suggestion to display the default state of the flags among a small info if the current settings is the default or not. The main goal was to harden the Browser to make it less vulnerable, less fingerprintable as well as overall more secure. Brave already now provides a reasonable secure and private Browser, which do not needs to be hardened anymore. The only suggestion someone can provide is to use xyz personal preferences which you can use, or not use, in the settings. However, most of those settings are not related to privacy or security at all - even tho it is misconstrued as such - e.g. turning off the wallet function to avoid connections to their services, when the reality is much different because connections are - in this example - only made when you actually try to use such a feature and they are NOT constantly established when you NOT use this, in other words, leaving such toggles as they are, in their default state, even if they are enabled are not related to privacy implications at all unless someone provides reasonable evidence that this is not the case, bugs etc. aside of course. That said, thanks for the ride. I am closing this project, thank the Chromium as well as Brave developers to enhance the default settings as well as the flags and their description. I have no plans to change any of the flags myself anymore which means that this the end of the project.
This repo is archived. You cannot comment on issues.
No Milestone
No Assignees
1 Participants
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: CHEF-KOCH/Brave-Browser-Hardening#1
No description provided.