Project

General

Profile

Feature #5751

Support Bluetooth when it's used at boot

Added by Tails almost 6 years ago. Updated over 3 years ago.

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

0%

Feature Branch:
Type of work:
Code
Blueprint:
Starter:
No
Affected tool:

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 System->Preferences->Bluetooth, to get a bluetooth keyboard working.

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


Related issues

Related to Tails - Feature #7787: Better document the (lack of) BlueTooth support in Tails Resolved 08/16/2014
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 12/29/2015

History

#1 Updated by intrigeri almost 6 years ago

  • 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 about 5 years ago

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

#3 Updated by BitingBird about 5 years ago

  • Category set to Hardware support

#4 Updated by intrigeri about 5 years ago

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

#5 Updated by sajolida almost 5 years ago

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

#6 Updated by intrigeri over 4 years ago

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 over 4 years ago

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 over 4 years ago

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

#9 Updated by intrigeri over 3 years ago

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

#10 Updated by intrigeri over 3 years ago

  • Status changed from Confirmed to Rejected

#10801 has the new plan.

#11 Updated by intrigeri almost 2 years ago

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

#12 Updated by u over 1 year ago

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

#13 Updated by u over 1 year ago

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

Also available in: Atom PDF