-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix Bluetooth readme #180
Comments
I do not see the contradiction. Is it the fact that we do not completely kill bluetooth but recommend not usinng it? 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. Killing bluetooth would strip the usre of the freedom of turning it on with a button. Maybe we can change the wording to something like:
|
So it's enabled.
So it's turned off, aka disabled. That seems like a contradiction?
That's alright.
For sure.
Yes. Not my goal to disable things to a level so the user cannot undo the configuration.
That sounds much better. No contradictions. Can take this one.
How? |
It seems it isn't quite clear what I mean by enabled, disabled or turned on/off. Disabling bluetooth means, there is no kernel module for bluetooth. Bluetooth is something that does not exist on the system. You can't see it, set it, configure it, do anything. Having bluetooth turned on or off means a software toggle. Literally the bluetooth turn on/off button in your GUI settings application. Normally bluetooth is 'on' when system boots up on debian. That means, it looks around and when a known device shows up, it auto connects and it is in some circumstances discoverable and/or visible and so on. Our default makes sure bluetooth is off on start. It can be turned 'on' the usual way. How? Click the bluetooth button in the settings app or on the tray and switch the toggle. It is just that. Bluetooth is turned off by default, so no vulnurability or explotation possible. It is off. But it can be turned on with one line of command or with a gui settings application in less than a second. So it is still enabled in the kernel. As in, kernel is able to use the protocol, it has the necessary modules. |
Much more clear now. Thank you! |
as suggested by @monsieuremre Kicksecure#180
Sounds like a contradiction.
The text was updated successfully, but these errors were encountered: