Repository navigation
fix Bluetooth readme #180
Description
Activity
Bluetooth is left enabled but users are highly discouraged from ever turning it on, due to its history of numerous security vulnerabilities.
So it's enabled.
Unlike the default settings, we start the system with bluetooth turned off.
So it's turned off, aka disabled.
That seems like a contradiction?
Is it the fact that we do not completely kill bluetooth but recommend not usinng it?
That's alright.
I take that it is more likely than not that the user will need to use bluetooth at some point. But given the option, the choice should be not using it.
For sure.
Killing bluetooth would strip the usre of the freedom of turning it on with a button.
Yes. Not my goal to disable things to a level so the user cannot undo the configuration.
Actually the opposite. I like the changes being documented with users having freedom and documentation available to do whatever they want despite any warnings in the documentation.Maybe we can change the wording to something like:
Bluetooth is 'enabled' for the system. Unlike the usual default behavior, we start bluetooth turned off on system start and it stays that way unless the user explicitly chooses to turn bluetooth on. The user is left with the freedom to easily switch bluetooth on and off the usual way with his own discretion. We set significantly more private defaults for bluetooth connections by enforcing private addresses and strict timeout settings for discoverability and visibility. That being said, the most secure and private bluetooth connection might inherently come with risks by its nature and may be prone to exploits, as it has a history of having new security vulnurabilities often. So users are recommended to choose not to use bluetooth when given the option.
That sounds much better. No contradictions. Can take this one.
easily switch bluetooth on and off the usual way
How?
Much more clear now. Thank you!
- added 2 commits that reference this issue
on Dec 25, 2023
Sounds like a contradiction.