Feature #5751

Support Bluetooth when it's used at boot

Added by Tails 2013-07-18 07:45:45 . Updated 2016-01-03 21:07:40 .

Status:
Rejected
Priority:
Normal
Assignee:
Category:
Hardware support
Target version:
Start date:
Due date:
% Done:

0%

Feature Branch:
Type of work:
Code
Blueprint:

Starter:
0
Affected tool:
Deliverable for:

Description

Do we want to support bluetooth somehow, or disable it more drastically? Enabling it would enable the use of some hardware, but what security / anonymity / privacy issues would it have? Beside, how much enabled is it already?

See Is there any bluetooth manager to set up mobile gprs?.

See what packages we should ship to support bluetooth hardware, for those who need it:

  • A user reported that they had to install gnome-bluetooth and go to SystemPreferences>Bluetooth, to get a bluetooth keyboard working.

Wait for protect against external bus memory forensics (Feature #5451).

Subtasks

Related issues

Related to Tails - Feature #7787: Better document the (lack of) BlueTooth support in Tails Resolved 2014-08-16
Related to Tails - Feature #5547: Deactivate PCMCIA, ExpressCard and FireWire if unused after 5 minutes Confirmed
Related to Tails - Feature #10801: Make bluetooth opt-in in the Greeter Confirmed 2015-12-29

History

#1 Updated by intrigeri 2013-07-19 07:02:43

  • Subject changed from support bluetooth? to support bluetooth when it's used at boot
  • Type of work changed from Wait to Code

#2 Updated by intrigeri 2014-05-02 13:29:47

  • Subject changed from support bluetooth when it's used at boot to Support bluetooth when it's used at boot
  • Description updated
  • Starter set to No

#3 Updated by BitingBird 2014-06-09 13:42:12

  • Category set to Hardware support

#4 Updated by intrigeri 2014-06-21 14:50:35

  • Subject changed from Support bluetooth when it's used at boot to Support Bluetooth when it's used at boot

#5 Updated by sajolida 2014-08-16 16:35:38

  • related to Feature #7787: Better document the (lack of) BlueTooth support in Tails added

#6 Updated by intrigeri 2015-01-02 14:22:02

This can’t really work, as Bluetooth requires some pairing between devices to happen, so we can’t automatically guess if Bluetooth is going to be useful without letting the user choose.

#7 Updated by intrigeri 2015-01-02 14:53:09

A plan could be:

  • at build time, blacklist bluetooth (bluetooth stack)
  • at (early) boot, rfkill block bluetooth config/chroot_local-includes/usr/local/sbin/tails-set-wireless-devices-state
  • in the Greeter, allow opting-in for Bluetooth
    • in PostLogin.default, pass Bluetooth user prefs to tails-unblock-network
    • in tails-unblock-network, if Bluetooth is enabled, remove the blacklist file and rfkill unblock bluetooth
  • later
    • for added safety, disable system-wide daemon and/or move gnome-bluetooth files out of the way?
    • hardware-dependent device drivers?
    • support enabling Bluetooth post-login if I forgot?

#8 Updated by BitingBird 2015-01-02 23:16:18

  • related to Feature #5547: Deactivate PCMCIA, ExpressCard and FireWire if unused after 5 minutes added

#9 Updated by intrigeri 2016-01-03 21:06:43

  • blocks deleted (Feature #5451: Protect against external bus exploitation)

#10 Updated by intrigeri 2016-01-03 21:07:40

  • Status changed from Confirmed to Rejected

Feature #10801 has the new plan.

#11 Updated by intrigeri 2017-09-14 07:40:37

  • related to Feature #10801: Make bluetooth opt-in in the Greeter added

#12 Updated by Anonymous 2018-01-19 14:21:45

  • related to Feature #10801: Make bluetooth opt-in in the Greeter added

#13 Updated by Anonymous 2018-01-19 14:21:50

  • related to deleted (Feature #10801: Make bluetooth opt-in in the Greeter)